[cfe-commits] r167567 - in /cfe/trunk: include/clang/Driver/Driver.h include/clang/Driver/Types.h lib/Driver/Driver.cpp lib/Driver/ToolChains.cpp lib/Driver/Tools.cpp lib/Driver/Tools.h lib/Driver/Types.cpp lib/Driver/WindowsToolChain.cpp

Joerg Sonnenberger joerg at britannica.bec.de
Tue Nov 13 00:10:02 PST 2012


On Mon, Nov 12, 2012 at 07:54:15PM -0800, Richard Smith wrote:
> On Mon, Nov 12, 2012 at 7:14 PM, Rafael EspĂ­ndola
> <rafael.espindola at gmail.com> wrote:
> >> Consider:
> >>
> >> cat << EOF > test.F
> >>       PROGRAM HELLOW
> >>       WRITE(UNIT=*, FMT=*) 'Hello World'
> >>       END
> >> EOF
> >>
> >> clang-cpp test.F
> >
> > This used to run
> > f951 test.F -cpp=/tmp/ccOj9mhO.f90 -E -quiet -v test.F -o - -m64
> > -mtune=generic -march=x86-64 -fsyntax-only
> >
> > Now it tries to run clang as a preprocessor and fails because of the
> > "-x f95-cpp-input". Is the fortran preprocessor the same as the c one?
> 
> It's similar, but not quite the same. There is a patch to support
> Fortran preprocessing in Clang:
> 
> http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120430/057199.html
> 
> (There's also Fortran 95's coco preprocessor, which is not the same at
> all, but I assume that's not what's wanted here.)

While I think proper support for the Fortran preprocessing rules would
be nice, I wonder if reverting this change for clang 3.2 is not the
better option?

Joerg



More information about the cfe-commits mailing list