search for: eopt

...int main() { const long a = foo(); const long b = foo(); const long res = a * b; fprintf(stderr, "0x%lx 0x%lx 0x%lx 0x%lx\n", res, a, b, res / a); return 0; } $ cat e2.c long foo(void) { return 0x100000000; } $ llvm-gcc --emit-llvm e.c -c -o e.bc $ opt -O3 e.bc -o=eopt.bc $ llc eopt.bc $ gcc -o e e2.c eopt.s $ ./e 0x0 0x100000000 0x100000000 0x100000000 I was expecting the 4th number to be 0, but the CES pass that res / a = a * res / a = b and so optimizes the division out. If I use directly a C compiler (same result with gcc, llvm-gcc or clang) I get the resul...

Hi Duncan, On Mon, Mar 9, 2015 at 10:40 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote: >> >> On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at gmail.com> >> wrote: >> > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote: >> >> Hi, >> >> >> >> [This

I have several related questions. 1. Is it possible to use a GUI: Rstudio/Eclipse/Visual-studio to debug compiled code on Windows? Things that work on Eclipse for Windows do not work on Eclipse for Windows. 2. R CMD INSTALL seems to override default attempts to provide CFLAGS="-DDEBUG -g3 -O0" 3. Is it necessary to compile R with debug turned on? One of the FAQs mentioned to

...the default if not > specified), I get the following error when R CMD INSTALL is trying to > create Rcpp.dll: > > collect2.exe: error: ld returned 5 exit status > > With -O1, -O2, or -O3, there is no error. > > - Hsiu-Khuern > The default is O2, I believe, as the default EOPTS in src/gnuwin32/Mkrules.dist are -O2 -mtune=core2. Avi

...external libs to 64bits object files) I would be very greatful if you could help me to compile R, please. Thank you very much !! ============== MkRules.local ============== G_FLAG=-gdwarf-2 LEA_MALLOC=YES USE_ATLAS=NO BINPREF64 = C:/Rtools/gcc-4.6.3/bin/ WIN = 64 BUILD_HTML = NO MIKTEX = TRUE EOPTS=-mtune=native OPENMP = -fopenmp PTHREAD = -pthread

...me directory as the debug version) gives the > same output as before. > > I'm happy to help but I appreciate this list might not be the best > place to get a tutorial on using gdb on Windows. Essentially, the steps are: build with DEBUG=T (to have debug symbols), possibly updating EOPTS in MkRules.local to disable optimizations, then run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then you can break to debugger from RGui menu, or just run the code that segfaults, and you get to gdb and can print the stacktrace, etc. You can find some information in...

...r what it is worth. If it helps, I have been using the following: Tarball - R-2.15.0.tar.gz Rtools - 2.15 CYGWIN 1.7 already installed (for ATLAS) so Rtools CYGWIN dlls NOT installed Tcl/tk, libjpeg, libpng, libtiff all installed cairo-current-win.tar.gz The only other change I made was to set EOPTS=-march=corei7 as the GCC included in the toolchain in 4.6.3 which recognizes the i7 (as opposed to Cygwin which is using 4.5.3 and only recognizes the core2). My computer is a Lenovo W520 with a Core i7 2760QM running Windows XP Professional. If there is any other information that would be helpf...

Hi, I am trying to make a debug version of R ( for use with gdb later ) on windows. I am executing the following. src\gnuwin32>make clean src\gnuwin32>make DEBUG=T? In the output, I see many -O3 flags I do not see any ?-g -O0 flags? which ( I believe/I think ) that is what I need to debug R in gdb. What is the proper way to 'make' a 'Debug version of R'? Thank you,

...;>> same output as before. >>> >>> I'm happy to help but I appreciate this list might not be the best >>> place to get a tutorial on using gdb on Windows. >> Essentially, the steps are: build with DEBUG=T (to have debug symbols), >> possibly updating EOPTS in MkRules.local to disable optimizations, then >> run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then >> you can break to debugger from RGui menu, or just run the code that >> segfaults, and you get to gdb and can print the stacktrace, etc. You can &...

...me directory as the debug version) gives the > same output as before. > > I'm happy to help but I appreciate this list might not be the best > place to get a tutorial on using gdb on Windows. Essentially, the steps are: build with DEBUG=T (to have debug symbols), possibly updating EOPTS in MkRules.local to disable optimizations, then run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then you can break to debugger from RGui menu, or just run the code that segfaults, and you get to gdb and can print the stacktrace, etc. You can find some information in...

...ves the same output as before. >> >> I'm happy to help but I appreciate this list might not be >> the best place to get a tutorial on using gdb on Windows. > Essentially, the steps are: build with DEBUG=T (to have > debug symbols), possibly updating EOPTS in MkRules.local > to disable optimizations, then run gdb loading RGui, "set > solib-search-path", run RGui from gdb. Then you can break > to debugger from RGui menu, or just run the code that > segfaults, and you get to gdb and can print the > stacktra...

...) gives the > > same output as before. > > > > I'm happy to help but I appreciate this list might not be the best > > place to get a tutorial on using gdb on Windows. > > Essentially, the steps are: build with DEBUG=T (to have debug symbols), > possibly updating EOPTS in MkRules.local to disable optimizations, then > run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then > you can break to debugger from RGui menu, or just run the code that > segfaults, and you get to gdb and can print the stacktrace, etc. You can > find som...

...before. > >>> > >>> I'm happy to help but I appreciate this list might not be the best > >>> place to get a tutorial on using gdb on Windows. > >> Essentially, the steps are: build with DEBUG=T (to have debug symbols), > >> possibly updating EOPTS in MkRules.local to disable optimizations, then > >> run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then > >> you can break to debugger from RGui menu, or just run the code that > >> segfaults, and you get to gdb and can print the stacktrace,...

...e texify # for texinfo >= 5.1. If the texinfo files are installed at /packages/texinfo, # TEXI2ANY = /path/to/perl -I/packages/texinfo /packages/texinfo/texi2any # if you do not have texinfo (default), # TEXI2ANY = missing # additional optimization flags (use -mtune=native for a private build) EOPTS = -mtune=native # define to -fopenmp if the toolchain has OpenMP support # OPENMP = -fopenmp # define to -pthread if the toolchain has pthreads support # PTHREAD = -pthread ## ====== configuration macros for building installer =========== # location where Inno Setup 5.[34].x was installed. Spa...

On Wed, Mar 11, 2015 at 1:40 AM, Hsiu-Khuern Tang <tangoh at gmail.com> wrote: > On Tue, Mar 10, 2015 at 8:54 PM, Avraham Adler <avraham.adler at gmail.com> wrote: >> >> I successfully rebuilt R-devel_2015-03-09 with the most recent version >> of Rtools tonight, building both ICU_531 and this time libcurl (7.39) >> as well (and OpenBLAS, of course). The

...t-win.tar.gz # and set CAIRO_HOME to the parent of the win32/win64 directories # # If CAIRO_HOME is not set the devices are not built. CAIRO_HOME = # set this to YES to build static HTML help BUILD_HTML = NO # unset this if you are *not* using MiKTeX MIKTEX = TRUE # additional optimization flags EOPTS=-mtune=core2 # define to -fopenmp if the toolchain has OpenMP support OPENMP = -fopenmp # define to -pthread if the toolchain has pthreads support PTHREAD = -pthread ## ====== configuration macros for building installer =========== # location where Inno Setup 5.[34].x was installed. Spaces all...

...If the texinfo files are installed at > /packages/texinfo, > # TEXI2ANY = /path/to/perl -I/packages/texinfo /packages/texinfo/texi2any > # if you do not have texinfo (default), > # TEXI2ANY = missing > > # additional optimization flags (use -mtune=native for a private build) > EOPTS = -mtune=native > > # define to -fopenmp if the toolchain has OpenMP support > # OPENMP = -fopenmp > > # define to -pthread if the toolchain has pthreads support > # PTHREAD = -pthread > > ## ====== configuration macros for building installer =========== > > # locatio...

...pile R on Windows 10 64-bit using LTO as I always do, I encountered a segmentation fault early in the compilation. I am uncertain as to what it means (please see below for error extract). I am using the most recent version of Rtools43 (5863) and updated its libraries prior to starting the build. My EOPTS is " -march=native -pipe -mno-rtm" and my LTO/LTO_OPT/LTO_FC/LTO_FC_OPT is "-flto=1 -fuse-linker-plugin". Any explanation or suggestions would be appreciated. Thank you, Avi ``` installing zoneinfo making console.d from console.c making dynload.d from dynload.c making embed...

Hi All, I am trying to compile R from source on a 64 bit Windows. I have downloaded and installed all the third party software as per the R - documentation. The compilation starts fine and after a while it stops with the following error message: D:/Rtools/mingw_64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.3/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lRgraphapp collect2.exe: error: ld

On Tue, Sep 8, 2020 at 11:44 PM Jeroen Ooms <jeroenooms at gmail.com> wrote: > > On Tue, Sep 8, 2020 at 5:20 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > > On 9/8/20 4:48 PM, Hugh Parsonage wrote: > > > Unfortunately I only get > > > > > > [Thread 21752.0x4aa8 exited with code 3221225477] > > > [Thread 21752.0x4514