| Re: .NOT. (Re: Not! Praise for Gfortran) :o) |
|
 |
|
 |
|
 |
|
 |
Group: comp.lang.fortran · Group Profile
Author: Ron FordRon Ford Date: Sep 19, 2008 15:48
On Fri, 19 Sep 2008 10:04:04 -0400, Paul van Delst posted:
> 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.
Really? I used the appropriate openmp flag for gfortran for the first time
a couple weeks back and Tobias Burns advised me so:
F:\gfortran\source>gfortran -o thread -fopenmp ff55.f90
Seems unambiguous enough. If there's anything I miss when I use gfortran
it's an IDE and visual debugger. The mingw people have one now for c/c++;
maybe in a year it will be adapted for fortran.
--
Historian: an unsuccessful novelist.
H. L. Mencken
| 
