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++/58308] Segmentation fault: internal compiler error: in make_decl_rtl, at varasm.c:1147 Date: Wed, 04 Sep 2013 08:45:00 -0000 [thread overview] Message-ID: <bug-58308-4-Wrp9tSAQbP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58308-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58308 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid, | |ice-on-invalid-code Known to fail| |4.7.3, 4.8.0 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- t.C: In function 'int main()': t.C:6:26: error: use of local variable with automatic storage from containing function int *p = &x; ^ t.C:3:11: note: 'int x' declared here int x = 666; ^
prev parent reply other threads:[~2013-09-04 8:45 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-03 17:38 [Bug c++/58308] New: " dmitriy-hshg at mail dot ru 2013-09-03 17:39 ` [Bug c++/58308] " dmitriy-hshg at mail dot ru 2013-09-04 8:45 ` rguenth at gcc dot gnu.org [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-58308-4-Wrp9tSAQbP@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).