public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [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) Date: Sun, 12 Apr 2020 16:33:11 +0000 [thread overview] Message-ID: <bug-53077-4-pic4uqkNBd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53077-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53077 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|dominiq at lps dot ens.fr |unassigned at gcc dot gnu.org --- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- Unassigning myself.
prev parent reply other threads:[~2020-04-12 16:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-22 20:34 [Bug fortran/53077] New: suggestion to add the .f extension to the list of file extensions that trigger enabling of the preprocessor 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 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 [this message]
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-pic4uqkNBd@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).