search for: ffloat

hi - in the context of funny problems with optim() -- bug report 671 -- Prof Brian Ripley wrote: > I think this is the usual problem with inconsistent internal precision > on Linux compilers, so try compiling optim.c with -ffloat-store to make > gcc IEEE-compliant. this was new to me, but then i am somewhat new to linux and gcc. a grep on the R-1.1.1 source dist'n does not match -ffloat-store. i've lately run into funny "jumps" while using optim(), similar to what was described in the original bug re...

Colleagues, I have a routine in package labdsv that calls a FORTRAN subroutine. Recently, I was informed that it sometimes gives different results on a PC and Mac, and that the PC version is clearly wrong. I tested it on linux (because I don't have a PC), and I get the same (incorrect) behavior as the PC. Simply by inserting debug WRITE statements in the FORTRAN I would get different,

...7849 0.2036804 which is simply plainly wrong and eigen(cbind(1, 3:1, 1:3), EISPACK=TRUE) gives the correct eigen values c(5, 1, 0) and corresponding eigenvectors. IIRC, we've already dealt with a Lapack problem, and that workaround (built into R-devel's Makefiles) has been to use -ffloat-store for the compilation of src/modules/lapack/dlamc.f ---------- Thank you for hints / suggestions. Others with 64-bit platforms might also try to see what eigen(cbind(1, 3:1, 1:3)) gives there. Martin Maechler

...removing the bounds. However, when bounds are added the snippet returns 'FALSE'. An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store --- > SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse Reverting to the old SAFE_FFLAGS 'solves' the problem. > sessionInfo() R version 3.5.2 (2018-12-20) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Scientific Linux release 6.4 (Carbon) Matrix products: de...

...me, a newcomer to building R as well as 64-bit R, in a useful direction. I have a dual Opteron 275 box running RedHat EL4. I ran configure successfully, and, then, get the following error while running make: make[4]: Entering directory `/tmp/R-2.2.0/src/modules/lapack' g77 -fPIC -g -O2 -ffloat-store -c dlamc.f -o dlamc.lo g77 -fPIC -g -O2 -c dlapack0.f -o dlapack0.lo g77 -fPIC -g -O2 -c dlapack1.f -o dlapack1.lo g77 -fPIC -g -O2 -c dlapack2.f -o dlapack2.lo g77 -fPIC -g -O2 -c dlapack3.f -o dlapack3.lo g77 -fPIC -g -O2 -c cmplx.f -o cmplx.lo g77 -fPIC -g -O2 -c cm...

Dear all, I have a big problem to compile R-3.0.2 on our SUSE SLES 11 Server. Make breaks up with fortran errors and so the installation isn't successful This is a part from the make run output.: gcc-3.3 -fpic -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3-hammer/ -lg2c -ffloat-store -c dlamch.f -o dlamch.o dlamch.f: In function `dlamch': dlamch.f:89: warning: INTRINSIC DIGITS, EPSILON, HUGE, MAXEXPONENT, Reference to unimplemented intrinsic `DIGITS' at (^) (assumed EXTERNAL) dlamch.f:89: INTRINSIC DIGITS, EPSILON, HUGE, MAXEXPO...

Full_Name: Sigbert Klinke Version: 2.1.1 OS: Suse Linux 10.0 (Full DVD) Submission from: (NULL) (141.20.100.252) Suse 10.0 installs only a Fortran 95 compiler with g77 compability mode. Using this leads in "configure" to an abortion with problems about "FPICFLAGS". Deinstalling g77 compatiblity mode, using f2c, compiles R. But after calling R() the program shows its entrance

We are trying to install R2.2.1 on a IBM P655 Cluster, SuSE LE 9.1 We are using gcc v 3.3.3 and we are getting this error on make g77 -fPIC -g -O2 -ffloat-store -c dlamc.f -o dlamc.lo g77 -fPIC -g -O2 -c dlapack0.f -o dlapack0.lo g77 -fPIC -g -O2 -c dlapack1.f -o dlapack1.lo g77 -fPIC -g -O2 -c dlapack2.f -o dlapack2.lo g77 -fPIC -g -O2 -c dlapack3.f -o dlapack3.lo g77 -fPIC -g -O2 -c cmplx.f -o cmplx.lo gcc -shared -L/usr/local/lib -o lib...

...ded the snippet returns 'FALSE'. > > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not > have the problem. Between the two versions R has changed the flags to > compile Fortran sources: > > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > --- > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > > >> sessionInfo() > > R version 3.5.2 (2018-12-20) > > Platform: x86_64-pc-linux-gnu (64-bi...

...ing to a similar issue, concerning gcc-3.4 and broken lapack libraries provided by FC3 (see https://stat.ethz.ch/pipermail/r-devel/2005-May/033117.html). Following these opinions/ findings, I did the following (though I knew that -- in principle -- R is supposed to handle this issue by passing a --ffloat-store flag to the fortran compiler, doesn't it?): * I wanted to remove the FC3 native lapack libraries, and to my surprise, they were not installed at all (no liblapack.so.xxx in /usr/lib). * I set up an older gcc environment, i.e. the last release from the 3.3.x family (3.3.6) and tried to re...

...s are added the snippet returns 'FALSE'. > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > --- > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > >> sessionInfo() > > R version 3.5.2 (2018-12-20) > > Platform: x86_...

...However, when bounds are added the snippet returns 'FALSE'. > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > --- >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > >> sessionInfo() > R version 3.5.2 (2018-12-20) > Platform: x86_64-pc-linux-gnu (64-bit) > Running under: Scientific Linu...

I've just installed gcc-3.4.0 on RH8.0 (on a dual athlon MP, if it matters) and rebuilt R. I find interSpline (in example(autoload)) is failing to complete. It seems to be looping in dlamc1 in dlapack0.f. This happened both with ATLAS and the BLAS built in to R. I will dig a little deeper, but it might be helpful to have a warning on record. -- Brian D. Ripley,

...s. However, when bounds are added the snippet returns 'FALSE'. > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > --- >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > Reverting to the old SAFE_FFLAGS 'solves' the problem. >> sessionInfo() > R version 3.5.2 (2018-12-20) > Platform: x86_64-pc-linux-gnu (64-bit) > Running unde...

...der so basically no optimizations are allowed. - this can be represented with a 'trapping_math' and/or 'signaling_NaN' bit, or maybe it can be encoded as 'no_reorder' 'no_duplicate' see: http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html (look for -ffloat-store) http://msdn.microsoft.com/en-us/library/e7s85ffb.aspx (Title: /fp (Specify Floating-Point Behavior)) - Morten

Does anybody know why two "-g" flags appear in the call to gcc in R CMD SHLIB Example: gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -fpic *-g* -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 *-g* -c c_file1.c -o c_object1.o Surely it need only be listed once? Alan [[alternative HTML version deleted]]

On Jan 14, 2010, at 2:01 AM, Duncan Sands wrote: > Hi Bill, > >> The current implementation of the "allow unsafe math" option is to >> specify it via the TargetOptions object. However, this prevents the >> target-independent optimizer from using it. Are there any opinions >> (ha!) on how this could be achieved in a nice clean manner which >>

...ippet returns 'FALSE'. > > > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > > --- > > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > > > >> sessionInfo() > > > R version 3.5.2 (2018-12-...

I'm having some trouble with optim(method="L-BFGS-B"), and I'm not sure I have the ability to track down and fix what seem to be bugs within optim(). I'm bootstrapping an original data set and fitting a model to each bootstrapped data set. For some bootstrapped samples, optim() sets negative parameter values (despite the fact that I have explicitly set non-zero lower

Dear list, When compiling the R-2.3.0 on FC4 x86_64, I got the following errors: make[3]: Entering directory `/project/scratch3/ligroup/wuming/src/R-2.3.0/src/main' gcc -Wl,--export-dynamic -L/usr/local/lib64 -o R.bin Rmain.o CConverters.o CommandLineArgs.o Rdynload.o Renviron.o RNG.o apply.o arithmetic.o apse.o array.o attrib.o base.o bind.o builtin.o character.o coerce.o colors.o complex.o