Questions and answers to many common issues and concerns.
Most of the problems reported by users have been encountered and solved before, or reflect a common misconception. This page lists problems and questions we have run into with the PGI® products, along with suggested solutions or workarounds.
A word about coding programs in a portable manner: Programs last much longer than anyone plans, especially if they work well. So it's a good idea to write them in a fashion that makes them independent of the machine or the compiler company you currently use. Often the response to a user's problem is that they are not coding in a portable fashion, because what they have done performs differently on different machines. Changing code now to remove platform/compiler dependencies can pay off in the long run.
-
Precision problems.
-
How come we get different answers on one platform versus a linux x86 platform?
-
When I execute, I get 'libpgc.so: cannot open shared object file'?roo
-
Do you have an example of using -byteswapio?
-
Do you have any relative performance numbers?
-
Does the license manager allow me to execute on other platforms?
-
read(9,rec=recnr,end=100,err=101,iostat=ios) acts different on other compilers
-
I have over 2GB of memory, but your compiled code can't handle even half of it?
-
When executing with -heapz set, why do I get a '0: mmap: Not enough space' error in PGHPF?
-
When executing, why do I get a stack overflow on Windows NT.
-
When I compile with -Ktrap=inexact, why does the program get so many exceptions?
-
When I compile with -Mvect=sse or -Mvect=prefetch, why do I get 'illegal instruction' exceptions when I run the program?
-
Linux 2.4 kernel supports > 2GB files - does pgf77/f90 support them?
-
Why does date_and_time(DATE) return 20 for the century?
-
I declared all my variables as 'REAL*8', yet I get different answers with '-r8' set. Why is that?