public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58835] [4.7/4.8/4.9 Regression] ICE with __PRETTY_FUNCTION__ in broken function Date: Thu, 20 Feb 2014 14:31:00 -0000 [thread overview] Message-ID: <bug-58835-4-DZ5AQ24c09@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58835-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58835 --- Comment #3 from Kai Tietz <ktietz at gcc dot gnu.org> --- Author: ktietz Date: Thu Feb 20 14:31:01 2014 New Revision: 207957 URL: http://gcc.gnu.org/viewcvs?rev=207957&root=gcc&view=rev Log: PR c++/58835 * semantics.c (finish_fname): Handle error_mark_node. Modified: branches/gcc-4_7-branch/gcc/cp/ChangeLog branches/gcc-4_7-branch/gcc/cp/semantics.c
next prev parent reply other threads:[~2014-02-20 14:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-22 3:17 [Bug c++/58835] New: " reichelt at gcc dot gnu.org 2013-10-23 8:06 ` [Bug c++/58835] " rguenth at gcc dot gnu.org 2014-02-20 14:28 ` ktietz at gcc dot gnu.org 2014-02-20 14:30 ` ktietz at gcc dot gnu.org 2014-02-20 14:31 ` ktietz at gcc dot gnu.org [this message] 2014-02-20 14:34 ` ktietz 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-58835-4-DZ5AQ24c09@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).