https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97031
--- Comment #2 from jean-pierre.flam...@univ-lille.fr --- Thanks, However, if I launch "man cpp" or "man gfortran" I can't see anything in relation with my problem and traditional. I just noticed that cpp recognizes the extensions .fpp .F and other uppercase extensions. This is why I added -cpp in the gfortran command (otherwise I have a diagnostic because of #ifdef's I have renamed my file with the .fpp extension; with "-cpp" in the gfortran submission I get the same errors. If I compile the file with extension *.f or .fpp without -cpp 1) the compilation has no error 2) a #ifdef...#endif is recognized even with a .f extension, without -cpp, in my simple example, (I should check that the directive really is taken into account !) 3) IF I compile my full project in a makefile, the absence of "-cpp" in the gfortran command induces a "Illegal preprocessor directive" error in all the routines having that #ifdef...#endif ----- Mail original ----- De: "kargl at gcc dot gnu.org" <gcc-bugzi...@gcc.gnu.org> À: "jean-pierre flament" <jean-pierre.flam...@univ-lille.fr> Envoyé: Samedi 12 Septembre 2020 12:14:06 Objet: [Bug fortran/97031] the content of a comment line breaks compilation https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97031 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #1 from kargl at gcc dot gnu.org --- (In reply to jean-pierre.flament from comment #0) > Created attachment 49211 [details] > contains fortran pgm, system and compile info and output > > I would like to signal to you a compilation problem that I have solved. > > the following comment line > > ! some text... DIR/*/) > > seems to put the compiler into trouble. (see attachment) > > changing the line to > > ! some text... DIR/d2) > > solves the problem > > The attached file contains > > 1) the fortran (self contained) > The faulty line is marked ==> FAULTY LINE, > it is followed by the line ===> LINE OK > 2) the system name (centos 6.10) and kernel > 3) the command to compile > 4) the output > > all these parts are sepaated by ============== lines > > I have also tested gfortran 6.3 (from devtoolset of centos) on the same > computer (As far as I remember the errors are different but the compilation > fails), and gfortran 4.9.3 also on a centos machine: same as 4.4.7). > Sorry I have not access to newer versions of gfortran This should be closed as INVALID. You are preprocessing your code with cpp in traditional mode, and therefore the '/*' in your code is the start of a C comment. This is an user error. Not a problem with gfortran.