[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2021-08-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662 Bug 28662 depends on bug 67623, which changed state. Bug 67623 Summary: interaction between cpp and Fortran https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67623 What|Removed |Added

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2015-08-30 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added CC|

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2015-08-18 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC|

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2014-12-11 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added CC||burnus at gcc

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2012-03-03 Thread fxcoudert at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662 Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed: What|Removed |Added CC|

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2008-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2008-08-06 06:24 --- For an initial, incomplete patch see: http://gcc.gnu.org/ml/fortran/2008-07/msg00248.html Slighly updated version. Set tradtional to 0 in fortran/cpp.c to enable new features, which will fail if the following

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2008-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2008-08-06 06:25 --- Created an attachment (id=16029) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16029action=view) libcpp patch (w/o setting traditional = 0 ) Said patch, see comment 7 for TODO items. --

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2008-07-30 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2008-07-30 18:06 --- For an initial, incomplete patch see: http://gcc.gnu.org/ml/fortran/2008-07/msg00248.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2008-04-23 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2008-04-23 19:29 --- Additional point, one needs to take care also of continuation lines of the following kind. This should print Hello Paul and not Hello Hans. #define Paul Hans ! Paul's string print *,'Hello Paul' end --

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2008-02-08 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2008-02-08 17:54 --- One big problem which prevents omitting the -traditional-cpp is that comments are not ignored. Another example of this is ! /* which is regarded as the beginning of a C/C++ comment. Thus we should add two

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2006-10-31 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2006-10-31 13:03 --- Confirm my bug. See also 29671 (# must be in the first column). -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2006-08-09 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-08-09 18:03 --- One problem without using -tranditional-cpp is that some tokens in C are not tokens in Fortran so you could get the wrong result. This is why -tranditional-cpp is used. There is no standard for Preprocessed

[Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x

2006-08-09 Thread tobias dot burnus at physik dot fu-berlin dot de
--- Comment #2 from tobias dot burnus at physik dot fu-berlin dot de 2006-08-09 18:10 --- One problem without using -tranditional-cpp is that some tokens in C are not tokens in Fortran so you could get the wrong result. This is why -tranditional-cpp is used. I though the