This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/67250] gfortran does not faithfully preprocess the way cpp does
- From: "pinskia at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 18 Aug 2015 05:41:48 +0000
- Subject: [Bug fortran/67250] gfortran does not faithfully preprocess the way cpp does
- Auto-submitted: auto-generated
- References: <bug-67250-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67250
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jeff Hammond from comment #7)
> And your "obvious workaround" is in fact not one because it changes the
> behavior of gfortran for Fortran source code and breaks the build in another
> way. And even if it did solve the problem, why not make it automatic with a
> flag to gfortran?
>
The only way is to use the workaround sorry. You could try -no-traditional-cpp
. But as you said it will break the build in a different way and that is
because the fortran code is not C code.
> The Intel Fortran compiler behaves as desired by default.
So. Using the C preprocessor is out side of the scope of the fortran standard
so different compilers will act differently.