I don't know if this applies to Seija's case, but one instance that I've ran
into when problem arose only with -O3 is uninitialized variables/arrays.
Adding the initialization fixed the problem. Just one thing to check, I guess.
Best,
Andy
From: Prof Brian Ripley
>
> It is likely that this i
It is likely that this is related to using higher-precision FPU
registers, in which case there is a portable solution: look up
SAFE_FFLAGS in 'Writing R Extensions'.
But if that is the cause, the real solution is to write the code using
proper convergence tests.
On Sat, 23 May 2009, Kasper D
On May 20, 2009, at 4:32 , Seija Sirkiä wrote:
Hello again,
thank you for the comments, especially this one:
Prof Brian Ripley wrote:
> My concern would be that there are different cases that fail under
> Fortran compiler X and you are just sweeping the problem under the
> carpet.
It inspir
Hello again,
thank you for the comments, especially this one:
Prof Brian Ripley wrote:
> My concern would be that there are different cases that fail under
> Fortran compiler X and you are just sweeping the problem under the
> carpet.
It inspired us to go back to search the cause, and we've ma
On Thu, 14 May 2009, Seija Sirkiä wrote:
Hello all,
it seems my efforts in reading the manuals and help files aren't enough so
here I am. The question is, how would I go about linking a pre-compiled DLL
in to my package? I have previously successfully built packages with Fortran
and C source
Hello all,
it seems my efforts in reading the manuals and help files aren't enough
so here I am. The question is, how would I go about linking a
pre-compiled DLL in to my package? I have previously successfully built
packages with Fortran and C source code, but now I'd like to take this
ready