[Bug fortran/94228] New: Preprocessor inconsistency for macros when invoked from gfortran

2020-03-19 Thread markwayne1969 at gmail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: markwayne1969 at gmail dot com Target Milestone: --- This report details differing behavior for preprocessor directives containing variadic macros when processed directly by cpp

[Bug fortran/94228] Preprocessor inconsistency for macros when invoked from gfortran

2020-03-19 Thread markwayne1969 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228 --- Comment #2 from Mark Paris --- (In reply to Andrew Pinski from comment #1) > gfortran defaults to -traditional-cpp preprocessor mode. Thank you for your reply. If I may, I'd like to pose a question that I cannot find the answer to from onlin

[Bug fortran/94228] Preprocessor inconsistency for macros when invoked from gfortran

2020-03-19 Thread markwayne1969 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228 --- Comment #4 from Mark Paris --- (In reply to kargl from comment #3) > No. Newer C, as opposed to older C, uses // for a comment. > Fortran uses // as the concatenation operator. Run this > through a cpp pre-processor. > > character(len=80)

[Bug fortran/94228] Preprocessor inconsistency for macros when invoked from gfortran

2020-03-22 Thread markwayne1969 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228 --- Comment #6 from Mark Paris --- (In reply to Steve Kargl from comment #5) > On Thu, Mar 19, 2020 at 10:24:10PM +0000, markwayne1969 at gmail dot com > wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228 > > >