public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeff.science at gmail dot com" <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: Tue, 18 Aug 2015 21:46:00 -0000 [thread overview] Message-ID: <bug-67250-4-4HkfuWV9wY@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 #13 from Jeff Hammond <jeff.science at gmail dot com> --- This is all fair. I try very hard to fix my own bugs and submit patches, but in this case I am wholly unqualified. I don't know the first thing about implementing a production compiler, or any compiler for that matter. I believe that some of my Intel colleagues contribute to GCC already. If I can figure out who they are, perhaps I can convince them to help here, since replicating the behavior of the Intel Fortran compiler has value for us. And yes, I did read a fraction of the gfortran manual (which google decided was relevant to my issue) in hopes of trying to solve this on my own. I confess to not having read the entire gfortran manual.
next prev parent reply other threads:[~2015-08-18 21:46 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 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 [this message] 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-4HkfuWV9wY@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).