public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slayoo at staszic dot waw.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53077] suggestion to add the .f extension to the list of file extensions that trigger enabling of the preprocessor
Date: Sun, 22 Apr 2012 21:36:00 -0000	[thread overview]
Message-ID: <bug-53077-4-oy9WqNLvXT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53077-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53077

--- Comment #2 from Sylwester Arabas <slayoo at staszic dot waw.pl> 2012-04-22 21:36:33 UTC ---
Hmm... apparently the PGI compiler uses the same rule for enabling preprocessor
with .f and .F extensions. Then, if there's some important reason behind it (?)
perhaps at least the warning message could be improved by indicating that the
preprocessor is off.


  parent reply	other threads:[~2012-04-22 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 20:34 [Bug fortran/53077] New: " slayoo at staszic dot waw.pl
2012-04-22 20:36 ` [Bug fortran/53077] " slayoo at staszic dot waw.pl
2012-04-22 21:36 ` slayoo at staszic dot waw.pl [this message]
2012-04-23  1:17 ` pinskia at gcc dot gnu.org
2012-04-23  8:27 ` burnus at gcc dot gnu.org
2012-04-23 11:13 ` slayoo at staszic dot waw.pl
2014-02-08 14:54 ` [Bug fortran/53077] replace "Illegal preprocessor directive" message with "Ignoring preprocessor directive at %C. Use -cpp to enable the C preprocessor" (a patch by Tobias included) dominiq at lps dot ens.fr
2020-04-12 16:33 ` dominiq at lps dot ens.fr

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-53077-4-oy9WqNLvXT@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: link
Be 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).