pperkins at ucsd.edu
Sat Nov 11 02:11:47 CET 2000
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 report. according to the gcc info page,
the "extra precision" (how can that be bad?) is a hardware-specific
issue. is there any store of R-knowledge on what hardware is affected
(i'm running on ppc -- the gcc info page mentions m68k and x86) and
what, if any, other routines might be affected?
along the same lines, is there an official R-stance on the accuracy of
libmoto for ppc? i remember having heard some vague mention on a ppc
newsgroup about the routines in libmoto being fast but not very
accurate. at one point, i compared results from R with libmoto to
something else and didn't find anything shocking.
thanks for any info.
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch
More information about the R-help