public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46855] [4.6 Regression] cc1plus: internal compiler error: Segmentation fault (instead of g++-4.5's: expected unqualified-id at end of input) Date: Wed, 08 Dec 2010 21:20:00 -0000 [thread overview] Message-ID: <bug-46855-4-NeOHOlr6XO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46855-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46855 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |error-recovery, | |ice-on-invalid-code Target Milestone|--- |4.6.0 Summary|cc1plus: internal compiler |[4.6 Regression] cc1plus: |error: Segmentation fault |internal compiler error: |(instead of g++-4.5's: |Segmentation fault (instead |expected unqualified-id at |of g++-4.5's: expected |end of input) |unqualified-id at end of | |input)
next prev parent reply other threads:[~2010-12-08 21:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-08 21:18 [Bug c++/46855] New: " gcc at abeckmann dot de 2010-12-08 21:20 ` rguenth at gcc dot gnu.org [this message] 2010-12-15 13:40 ` [Bug c++/46855] [4.6 Regression] " jakub 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-46855-4-NeOHOlr6XO@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).