Re: [Rcpp-devel] Optimization flag may be needed in Makevars.win for 4.9.2 toolchain

By default, it is "-g -O2" if you don't change before compiling R. I have asked once and R core team said there will be problems using "-O3" for some packages. Best wishes, KK On Tue, Aug 25, 2015 at 7:47 PM, Dirk Eddelbuettel wrote: > > On 25 August 2015 at 16:02, Kevin Ushey wrote: > | Does

Re: [Rcpp-devel] Optimization flag may be needed in Makevars.win for 4.9.2 toolchain

On 25 August 2015 at 16:02, Kevin Ushey wrote: | Doesn't CRAN R default to using -O2 flags when compiling C++ source | files? (I think the default is -O3 for C source files). | | Are you using CRAN R, or a locally built R? You might need to set that | explicitly yourself when configuring R? Opti

Re: [Rcpp-devel] Optimization flag may be needed in Makevars.win for 4.9.2 toolchain

Doesn't CRAN R default to using -O2 flags when compiling C++ source files? (I think the default is -O3 for C source files). Are you using CRAN R, or a locally built R? You might need to set that explicitly yourself when configuring R? On Tue, Aug 25, 2015 at 2:54 PM, Avraham Adler wrote: > The -

Re: [Rcpp-devel] Optimization flag may be needed in Makevars.win for 4.9.2 toolchain

The -march is local, of course. The question is should Rcpp always enforce at least -O2 or the like? From your answer I guess not. The reason why not to simply have an optimization flag in the local makevars is that, at least in my experience, some code is faster with O2 and some with O3, and by h

Re: [Rcpp-devel] Optimization flag may be needed in Makevars.win for 4.9.2 toolchain

On 25 August 2015 at 17:39, Avraham Adler wrote: | I've been testing a GCC 4.9.2-based toolchain for Windows for the last | week or so, and today fell afoul of the error uncovered here | . I've | been passing different optimization fla