Re: [R-pkg-devel] Compiler optimization flags with R package

2017-06-18 Thread Dirk Eddelbuettel
On 18 June 2017 at 09:22, Guillaume Chapron wrote: | Thanks! | | In that file, I see: | | CC = clang | CFLAGS = -Wall -mtune=core2 -g -O2 $(LTO) | | will having -O0 instead give me all the variables or is there a flag for better debugging (I guess -g does it a little already)? Right, -g is wh

Re: [R-pkg-devel] Compiler optimization flags with R package

2017-06-18 Thread Guillaume Chapron
Thanks! In that file, I see: CC = clang CFLAGS = -Wall -mtune=core2 -g -O2 $(LTO) will having -O0 instead give me all the variables or is there a flag for better debugging (I guess -g does it a little already)? Thanks again > On 17 Jun 2017, at 21:57, Dirk Eddelbuettel wrote: > > > On 17

Re: [R-pkg-devel] Compiler optimization flags with R package

2017-06-17 Thread Dirk Eddelbuettel
On 17 June 2017 at 21:32, Guillaume Chapron wrote: | I am trying to debug some C code that is run only through a R package. I debug with lldb but I always get a message telling that the package "was compiled with optimization - stepping may behave oddly; variables may not be available.” And in

[R-pkg-devel] Compiler optimization flags with R package

2017-06-17 Thread Guillaume Chapron
Hello, I am trying to debug some C code that is run only through a R package. I debug with lldb but I always get a message telling that the package "was compiled with optimization - stepping may behave oddly; variables may not be available.” And in fact, I cannot evaluate all variables and unde