public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/67250] gfortran does not faithfully preprocess the way cpp does Date: Mon, 17 Aug 2015 20:01:00 -0000 [thread overview] Message-ID: <bug-67250-4-Sp0vfQhbnz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67250-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67250 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Jeff Hammond from comment #3) > Unfortunately, this does not change anything. > I saying gfortran defaults to that and you can use that option to cpp to get the same behavior. > > gfortran-5 -traditional-cpp -I. -E source.F > # 1 "source.F" > # 1 "<built-in>" > # 1 "<command-line>" > # 1 "source.F" > C > C OLD SCHOOL COMMENTS > C > subroutine xyz(stuff) > implicit none > > # 1 "header.fh" 1 > ! comment > integer foo > external foo > # 7 "source.F" 2 > integer stuff > integer err_##handle; integer l_##handle,k_##handle; > err_##handle=foo(100,#handle,l_##handle,k_##handle); if > (.not.err_##handle) call bar("PUSH"#handle,#100); > print*,stuff > return > end
next prev parent reply other threads:[~2015-08-17 20:01 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-17 15:59 [Bug fortran/67250] New: " jeff.science at gmail dot com 2015-08-17 16:19 ` [Bug fortran/67250] " pinskia at gcc dot gnu.org 2015-08-17 16:43 ` manu at gcc dot gnu.org 2015-08-17 20:01 ` pinskia at gcc dot gnu.org [this message] 2015-08-17 21:07 ` kargl at gcc dot gnu.org 2015-08-18 5:34 ` jeff.science at gmail dot com 2015-08-18 5:41 ` pinskia at gcc dot gnu.org 2015-08-18 6:03 ` jeff.science at gmail dot com 2015-08-18 6:13 ` pinskia at gcc dot gnu.org 2015-08-18 6:28 ` sgk at troutmask dot apl.washington.edu 2015-08-18 21:46 ` jeff.science at gmail dot com 2015-08-19 12:46 ` manu at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-67250-4-Sp0vfQhbnz@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).