Search found 1103 matches

by jtull
Thu Apr 19, 2018 2:00 pm
Forum: Licenses and Installation
Topic: Version of vendor daemon is too old
Replies: 2
Views: 4720

The 18.* compilers use the same license file as older releases, but flexlm reported their utils had a security issue, so we restricted 18.* compilers and newer will need the 11.14.* release of pgroupd or newer. pgroupd -v returns the version. So if you use old versions of pgroupd, older compiler rel...
by jtull
Thu Apr 12, 2018 9:53 am
Forum: General Programming
Topic: Error when building ICON (CMAQ 5.0.2)
Replies: 2
Views: 2004

The difference between include foo and #include foo is that "include foo" inserts the code at compile time, and "#include foo" inserts the source at preprocessor time. If there are any preprocessor statements in the file foo, they will not be handled properly with "include foo" For example, the back...
by jtull
Thu Apr 12, 2018 9:44 am
Forum: General Programming
Topic: over 20GB arraysize
Replies: 2
Views: 1684

Hello, Virtual memory managers do have limits, and it is the Operating System that provides them. If you can write the same program in Microsoft Visual C and it works, but pgcc and pgfortran does not, then there is something to investigate. On my windows 10 laptop, with 17.10 and 32GB PGI$ pgfortran...
by jtull
Tue Apr 10, 2018 10:11 am
Forum: General Programming
Topic: OMP_DISPLAY_ENV
Replies: 3
Views: 2097

That is an openmp 4.5 environment variable, and is currently only supported on LLVM compilers. Add -Mllvm to your compilation, and the environment variable should work. % setenv OMP_NUM_THREADS 4 % setenv OMP_DISPLAY_ENV .TRUE. % pgfortran -mp -o m2 m2.f % m2 c= 30201.00 302000.0 30201.00 302000.0 d...
by jtull
Tue Apr 10, 2018 9:44 am
Forum: General Programming
Topic: Library Compatibility - gfortran and pg compilers (on OS/X)
Replies: 2
Views: 1724

The short answer to compatibility between pgfortran and gfortran (and intel fortran) is that they are not compatible. The longer, more technical answer is that if the fortran routine called from a different compiler had all of its arguments as pass by reference fortran 77 type, and had no I/O stmts ...