PGI / Flang compilers not working

[scivision]

Due to bug(s) in PGI / Flang, the stdlib io and optval don't build. There are spurious errors like

PGF90-F-0000-Internal compiler error. interf:new_symbol, symbol not found     630  (src/tests/io/test_loadtxt.f90: 2)

fiddling around with the code, PGI will even give a similar error for implicit none

Basically this seems a lot like other cases where there were bugs in PGI / Flang and not something wrong with stdlib. I did some attempts at workarounds in https://github.com/scivision/stdlib/tree/qp_opt

One could file a bug report with each of PGI and Flang, as the error is effectively identical, perhaps boiling it down to a minimum working example.

[certik]

Is the issue around quadruple precision?

[scivision]

Quadruple precision was part of the issue which I fixed with the #ifdef REAL128. However this remaining issue seems to be an actual compiler bug.

[certik]

If it's too much of a hassle, we can wait with officially supporting Flang until they fix such issues.

[rweed]

I've had similar issues with PGI and flang. I tried compiling my hashMap routines and both gave the same error (but with different equally confusing messages). I reported this to PGI about 1.5 years ago and haven't heard anything from them. Hopefully, flang/f18 will be more robust but I wouldn't rely on current PGI building anything that uses any OO features.

[scivision]

My opinion on PGI & Flang re: stdlib is to wait for the next releases of PGI & Flang. They've each made a lot of progress in 2019 w.r.t. Fortran 2008 support.

• expect no-charge PGI 20.4 in April-May 2020 if prior years' release schedule holds
• F18 is anticipated to come with LLVM 11 (F18 just missed the LLVM 10 merge window in Jan 2020)