search for: tkoen

Hi Steve, > With the caveat that one may need to use the VALUE attribute to > account for pass-by-value vs pass-by-reference. LAPACK should be all pass by reference, it is old F77-style code (except that the odd ALLOCATABLE array has snuck in in the testing routines).

Hi, gfortran trunk and 9-branch now have an option to automatically generate C prototypes for old-style F77 procedures. I just did for a in *.f; do gfortran -fsyntax-only -fc-prototypes-external $a > ${a%.f}.h; done in the src/modules/lapack directory. This generates header files which contain prototypes like int ilaenv_ (int *ispec, char *name, char *opts, int *n1, int *n2, int *n3,

Hi, there can be an issue with recent gcc where the system-installed "ar" and "ranlib" commands cannot handle LTO binaries. On compilation, this manifests itself with error messages claiming that they need extra plugins. This can be fixed by using the command line $ AR=gcc-ar RANLIB=gcc-ranlib ./configure --enable-lto so it is not a big issue, but it would still be nicer

Hi Tomas, > On 4/23/19 2:59 PM, Thomas K?nig wrote: >> Hi, >> >> there can be an issue with recent gcc where the system-installed "ar" >> and "ranlib" commands cannot handle LTO binaries.? On compilation, this >> manifests itself with error messages claiming that they need extra >> plugins. > Thanks for the report. What was the

Hi Peter, we (the gfortran team) are currently discussing this at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329 . I invite everybody who has an interest in this topic to take part in the discussion there. > Workarounds/solutions include: > > - disable certain optimizations -- works for now, but doesn't remove the root cause so seems generally fragile That looks like a

Hi Tomas, thanks a lot for your analysis. I have created https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329 for this, and put you in CC (if your e-mail address for GCC bugzilla is still current). Regards Thomas

Hi, I have tried to pinpoint potential problems which could lead to the LAPACK issues that are currently seen in R. I built the current R trunk using AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto --enable-BLAS-shlib=no --without-recommended-packages and used this to find problem areas. There are quite a few warnings that were flagged, due to mismatches in function