[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

[Hal Finkel]

----- Original Message -----
> From: "Joerg Sonnenberger" <joerg at britannica.bec.de>
> To: cfe-commits at cs.uiuc.edu
> Sent: Wednesday, November 14, 2012 10:39:55 AM
> Subject: Re: [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
> 
> On Tue, Nov 13, 2012 at 05:44:25PM -0600, Hal Finkel wrote:
> > If you just need preprocessing, then adding some file types so make
> > the compiler treat the source like C should work perfectly (that
> > is,
> > after all, what most of the original Fortran preprocessors did as
> > far
> > as I know). For anything more involved, we might want to revert
> > this
> > and do some more planning.
> 
> I don't know enough Fortran to decide whether e.g. the concat
> difference
> between traditional and ANSI C makes a difference etc. Anyone with a
> large enough source base to run tests between preprocessing with the
> "old" code and with explicit -x c?

For one thing, gfortran uses the traditional (pre-ANSI) preprocessing mode for Fortran files, while ifort (and most other vendor Fortran compilers I've tested) use ANSI mode.

C. Bergström, can you please comment on the "correct" preprocessor configuration for Fortran files? Are there any tokenization changes that are really required (and are there any that are just convenient to have)?

> 
> Joerg
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
> 

-- 
Hal Finkel
Postdoctoral Appointee
Leadership Computing Facility
Argonne National Laboratory