public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/30786] [4.1/4.2/4.3 Regression] ICE on _Pragma at end of file Date: Sun, 19 Aug 2007 18:55:00 -0000 [thread overview] Message-ID: <20070819185440.2391.qmail@sourceware.org> (raw) In-Reply-To: <bug-30786-9631@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from tromey at gcc dot gnu dot org 2007-08-19 18:54 ------- What does a plain "_Pragma" mean? Currently we try to give an error for this. However, it is not clear that this is actually erroneous. The copy of the standard that I am reading only mentions: A unary operator expression of the form: _Pragma ( string-literal ) ... but a plain _Pragma does not have that form. I'm not even sure that _Pragma(something-other-than-string-literal) should be recognized (but I'm new to C standardese...) Perhaps I have the wrong version of the standard or perhaps there is some more recent development of which I'm unaware. Anyway if we assume that a plain _Pragma is not an error then the first patch here is close to the correct one -- it just returns the plain _Pragma to the FE as an identifier. If all forms other than the full form are unrecognized then I think this first patch is correct. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30786
next prev parent reply other threads:[~2007-08-19 18:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-13 14:23 [Bug preprocessor/30786] New: " truedfx at gentoo dot org 2007-02-13 15:55 ` [Bug preprocessor/30786] " tromey at gcc dot gnu dot org 2007-02-16 2:03 ` [Bug preprocessor/30786] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2007-02-19 21:08 ` mmitchel at gcc dot gnu dot org 2007-04-16 19:11 ` bonzini at gnu dot org 2007-04-16 19:24 ` bonzini at gnu dot org 2007-08-06 15:08 ` pinskia at gcc dot gnu dot org 2007-08-19 16:13 ` tromey at gcc dot gnu dot org 2007-08-19 18:19 ` tromey at gcc dot gnu dot org 2007-08-19 18:55 ` tromey at gcc dot gnu dot org [this message] 2007-08-25 18:42 ` tromey at gcc dot gnu dot org 2007-10-31 14:50 ` tromey at gcc dot gnu dot org 2007-11-01 18:28 ` [Bug preprocessor/30786] [4.1/4.2 " jakub at gcc dot gnu dot org 2008-07-04 21:57 ` [Bug preprocessor/30786] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-30 21:33 ` jsm28 at gcc dot gnu dot 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=20070819185440.2391.qmail@sourceware.org \ --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).