public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/16586] [3.3/3.4 Regression] -O3 -fno-gcse ICE verify_local_live_at_start flow.c:575 Date: Fri, 16 Jul 2004 13:38:00 -0000 [thread overview] Message-ID: <20040716133820.8104.qmail@sourceware.org> (raw) In-Reply-To: <20040716071005.16586.ned@bike-nomad.com> ------- Additional Comments From bangerth at dealii dot org 2004-07-16 13:38 ------- Confirmed. In fact, with the following snippet I can also crash 3.4, so it doesn't seem to be fixed there but only papered over: ---------------- struct Ptrs { int (*ptr1)(int offset); int (*ptr2)(); } * ptrs; static int ** state; int foo(int stackIndex) { int *p; int sz; int objOop; int i; int **pp; ptrs->ptr1(stackIndex); if (ptrs->ptr2()) { return 0; } if (!((ptrs->ptr2()) == 0)) { return 0; } sz = ptrs->ptr2(); if (sz > 1) return 0; pp = state; for (i = 0; i <= sz-1; ++i) { objOop = ptrs->ptr1(0); if (!ptrs->ptr2()) return 0; *p = objOop; pp[i] = p; } } -------------------------- g/x> /home/bangerth/bin/gcc-3.3.4-pre/bin/gcc -O3 -c -fno-gcse x.i x.i: In function `foo': x.i:33: internal compiler error: in verify_local_live_at_start, at flow.c:575 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. g/x> g/x> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -O3 -c -fno-gcse x.i x.i: In function `foo': x.i:33: internal compiler error: in verify_local_live_at_start, at flow.c:546 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. W. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Known to work|3.4.0 3.5.0 3.0.4 |3.5.0 3.0.4 Last reconfirmed|0000-00-00 00:00:00 |2004-07-16 13:38:19 date| | Summary|[3.3 Regression] -O3 -fno- |[3.3/3.4 Regression] -O3 - |gcse ICE |fno-gcse ICE |verify_local_live_at_start |verify_local_live_at_start |flow.c:575 |flow.c:575 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16586
next prev parent reply other threads:[~2004-07-16 13:38 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-16 7:10 [Bug c/16586] New: gcc 3.3.3/3.3.4 " ned at bike-nomad dot com 2004-07-16 7:11 ` [Bug c/16586] " ned at bike-nomad dot com 2004-07-16 7:32 ` [Bug rtl-optimization/16586] [3.3 Regression] " pinskia at gcc dot gnu dot org 2004-07-16 11:04 ` gdr at gcc dot gnu dot org 2004-07-16 13:38 ` bangerth at dealii dot org [this message] 2004-07-28 20:43 ` [Bug rtl-optimization/16586] [3.3/3.4 " pinskia at gcc dot gnu dot org 2004-08-16 14:23 ` reichelt at gcc dot gnu dot org 2004-08-29 18:11 ` mmitchel at gcc dot gnu dot org 2004-08-29 18:25 ` mmitchel at gcc dot gnu dot org 2004-09-10 15:08 ` [Bug rtl-optimization/16586] [3.3 " reichelt at gcc dot gnu dot org 2004-09-10 19:18 ` rth at gcc dot gnu dot org 2004-09-16 14:12 ` [Bug rtl-optimization/16586] [3.3/3.4 " reichelt at gcc dot gnu dot org 2004-11-01 0:46 ` mmitchel at gcc dot gnu dot org 2004-12-02 7:11 ` ebotcazou at gcc dot gnu dot org 2004-12-05 9:39 ` ebotcazou at gcc dot gnu dot org 2005-05-19 17:48 ` mmitchel 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=20040716133820.8104.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).