Dear Lassi A. Tuura, you wrote on Today:
> > I'd be grateful if you detail a bit about this compiler's peculiarities.
> > To date, xlf is still my favourite, perhaps Microsoft can beat him... :-)
>
> df cannot do any form of useful preprocessing; this build system uses
> gcc -traditional (without #line directives) to do it. Basically xlf is
> on par there though, I had to do the same thing for it... End result:
> the generated makefiles have an intermediate stage for these two
> compilers.
That's neither exceptional nor really problematic. I am confident
the new Fortran/cpp macros I am developing will handle this.
(In fact, I'd be grateful if you could do a test on Windows for them
with this compiler; I know nothing about how autotools work on Windows
/Cygwin etc.).
> df does not understand paths with forward slashes.
> Something like `df foo/bar.f' will result in a message in the spirit of
> `bar.f: unknown option; do not know what do with foo'. The forward
> slashes must be converted into backslashes before df gets to see them.
> This is doable under cygwin + make, but nowhere pretty enough that I
> would have wanted to do it under autoconf, but then again, maybe it
I'd assume the autoconf core handles these issues, but I'm not certain.
> Oh and of course it has different function naming conventions, you'll
> have to force it to stick underscores at the end of the names and to
> lowercase them if those are the conventions you are used to in your
> mixed-language programs. The magic keywords are `-names:lowercase',
> `-assume:underscore'.
Have you tried the F77_NAME_MANGLING stuff in autoconf? I wonder whether
it can figure out df's behaviour. If it can't we should improve it.
> I seem to be using `-c -Tffile.f -Foout.obj' to compile. Can't remember
> why anymore. Oh, could be that it wanted `.for' by default, not the
> standard `.f'.
So there *is* a way to convince it to process .f files - IMO that's all
that counts. (unlike your old xlf :-( )
>From what you wrote so far, this compiler doesn't beat xlf.
I think it wouldn't even deserve a top 3 rank in the "weirdest fortran
compilers" list.
--
Martin Wilck <[EMAIL PROTECTED]>
Institute for Tropospheric Research, Permoserstr. 15, D-04318 Leipzig, Germany
Tel. +49-341-2352151 / Fax +49-341-2352361
