OK, I think someone does need to look at PGI Fortran and the LAPACK 3.3.0 test suite after all. At present, validating a full ATLAS build is not a definite success.
After talking to the LAPACK support team, it seems that the LAPACK test suite is more of an implementation torture test, rather than a validation that you have built LAPACK successfully. Some number of failures is therefore expected. Basically, I am told that, if you grep the output files of the test suite for “out of”, a successful build should expect between 200-500 failed tests. If there is a serious problem, there will be >1000 failed tests.
When I run the tests against the 32-bit PGI Linux compiler (10.0 and 11.3), with everything compiled with “-O0 -Kieee”, I get 267 numerical failures. This is good and is around what I get with both the GNU and Intel compilers.
When I do the same, but instead against the 64-bit PGI Linux compiler (10.0 and 11.3), I get 850 numerical errors. This is not so good.
I reported this to the LAPACK team, but have so far not had a response. From previous conversations with them, they do not seem to be regularly testing against PGI. The 850 errors may therefore be a problem.
To recap, I am:
- On a 64-bit Linux RHEL 5.5 system with Intel Nehalem processors.
- Compiling with either 64-bit PGI 10.0 or 11.3 Fortran compilers (same result with either)
- Building the netlib reference BLAS with “-O0 -Kieee”
- Checking that the reference BLAS passes the BLAS test suite
- Building the netlib LAPACK 3.3.0 with “-O0 -Kieee”
- Checking that the result passes the LAPACK 3.3.0 test suite.
I am doing this in order to validate a LAPACK library, so that I can use it to do a full BLAS/LAPACK build of ATLAS.
Have other people seen the same thing?