public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60193] New: [4.7.4/4.8/4.9 regression] ICE on big nested frame Date: Fri, 14 Feb 2014 09:29:00 -0000 [thread overview] Message-ID: <bug-60193-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60193 Bug ID: 60193 Summary: [4.7.4/4.8/4.9 regression] ICE on big nested frame Product: gcc Version: 4.7.4 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: ebotcazou at gcc dot gnu.org CC: ktietz at gcc dot gnu.org Depends on: 56807 Target: x86_64-*-mingw The fix for PR target/56807 has introduced ICEs on big nested frames: eric@polaris:~/gnat/bugs/N213-061> cat t.c void foo (int i) { void nested (void) { char arr[1U << 31]; arr[i] = 0; } nested (); } eric@polaris:~/gnat/bugs/N213-061> ~/gnat/gnat7_47/x86_64-pc-mingw32/gcc/cc1 -quiet t.c t.c: In function 'nested': t.c:7:3: internal compiler error: in change_address_1, at emit-rtl.c:2001 Please submit a full bug report, with preprocessed source if appropriate. Contact <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2014-02-14 9:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-14 9:29 ebotcazou at gcc dot gnu.org [this message] 2014-02-14 9:39 ` [Bug target/60193] " rguenth at gcc dot gnu.org 2014-02-14 9:39 ` ktietz at gcc dot gnu.org 2014-02-14 9:51 ` ktietz at gcc dot gnu.org 2014-02-14 10:00 ` ebotcazou at gcc dot gnu.org 2014-02-14 11:03 ` ktietz at gcc dot gnu.org 2014-02-14 11:52 ` ktietz at gcc dot gnu.org 2014-02-18 12:49 ` ktietz at gcc dot gnu.org 2014-02-18 12:53 ` [Bug target/60193] [4.7/4.8 " jakub at gcc dot gnu.org 2014-02-18 12:58 ` ktietz at gcc dot gnu.org 2014-02-18 13:47 ` ktietz at gcc dot gnu.org 2014-02-18 13:49 ` 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-60193-4@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).