Consider a trivial program:
end program foo
pgfortran -DMACRO="‘Hello World’" trivial.F90 && ./a.out
This compiles and executes as expected
pgfortran -E translates as expected
pgfortran -F destroys the file.
Understandable because .F90 and .f90 will be treated by MacOS as the same name (although it begs the question of why it works without -F … other compilers in other environments don’t).
Since the FreePGI for MacOS X is mac specific, seems like the driver ought to “know” that MacOS filesystems of the default kind will fail this way, and protect the user.
Or am I missing something from the documentation?