Bug in wave.F if PGI16 not defined (5.4.4)

Problems running VASP, runtime errors, technical questions.
Please check whether the answer to your question is given in
the VASP online manual or has been discussed in this forum

Moderators: Moderator, Global Moderator

Bug in wave.F if PGI16 not defined (5.4.4)

Postby ehermes » Mon Aug 14, 2017 7:04 pm

There appears to be a bug in the wave.F file that occurs when VASP is compiled without defining PGI16 (which I assume is meant only to be used with the Portland Group compilers version 16). Specifically, lines 209, 242, and 263 contain "#ifndef PGI16", whereas line 179 also contains this statement but it is commented out (!#ifndef PGI16). If PGI16 is not defined, then the arrays CPTWFP, CPROJ, and CR are defined to be contiguous pointer arrays, and if PGI16 is defined they are merely pointer arrays. Since the check on line 179 is commented out (along with the continuous pointer array declaration), CPTWFP and CPROJ are always declared to be regular (non-contiguous) pointer arrays regardless of whether PGI16 is defined. This results in a compiler error when using the Intel compilers version 13. Uncommenting lines 179-184 and 187 fixes the issue, and this seems to create a perfectly working executable.
Posts: 11
Joined: Tue May 14, 2013 5:45 pm

Return to Bugreports

Who is online

Users browsing this forum: No registered users and 1 guest