| .NOT. (Re: Not! Praise for Gfortran) :o) |
|
 |
|
 |
|
 |
|
 |
Group: comp.lang.fortran · Group Profile
Author: Paul van DelstPaul van Delst Date: Sep 19, 2008 07:04
Arjen Markus wrote:
> On 19 sep, 15:27, "Carlie J. Coats" jyarborough.com> wrote:>
> I got it, I compiled the file bilin.f - no problem. Then
> I compiled it with the option -openmp that I saw in your
> compile statement ... and got the file "penmp" instead
> of bilin.o !
>
> I do not know if gfortran supports OpenMP, but at least the
> flag -openmp seems to be interpreted as -o "penmp", setting
> the output file.
Wow, good catch.
However, judging from the liberal sprinkling of "*this*" and "THAT!" in the original post,
I doubt the attitude towards gfortran is going to change too much.
FWIW, gfortran is now my main development compiler for the radiative transfer model we
work on here at JCSDA/NCEP. All Fortran95 with structures and pointers a-go-go (carefully
designed usage, of course :o) compiles and runs no worries. I have many more issues with
commercial compilers (of which I use 3 on my linux box).
cheers,
paulv
| 
