public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matz at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27409] New: ICE in get_constraint_for_component_ref Date: Wed, 03 May 2006 15:46:00 -0000 [thread overview] Message-ID: <bug-27409-183@http.gcc.gnu.org/bugzilla/> (raw) The below testcase ICEs in get_constraint_for_component_ref when compiled with -O1 or beyond on x86_64. Richard mentions that it also fails with trunk. --------------------------------------- /* compile with gcc -c -Os -o foo.o foo.c */ typedef struct { struct { } z; } thang_t; struct widget { struct widget *p, *q; }; typedef struct thing { struct widget x; } thing_t; struct { int a; int b; int c; int d; int e; thang_t f; thing_t g; } my_struct; static void foo(thang_t *r) { splat(r);} void function(int blaz) { foo(&my_struct.f);} --------------------------------------- -- Summary: ICE in get_constraint_for_component_ref Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: matz at suse dot de GCC host triplet: x86_64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27409
next reply other threads:[~2006-05-03 15:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-03 15:46 matz at suse dot de [this message] 2006-05-03 16:05 ` [Bug middle-end/27409] " rguenth at gcc dot gnu dot org 2006-05-03 16:06 ` rguenth at gcc dot gnu dot org 2006-05-03 16:12 ` [Bug middle-end/27409] [4.1/4.2 Regression] " rguenth at gcc dot gnu dot org 2006-05-03 16:13 ` rguenth at gcc dot gnu dot org 2006-05-03 17:53 ` matz at suse dot de 2006-05-03 17:54 ` matz at suse dot de 2006-05-07 21:04 ` rguenth at gcc dot gnu dot org 2006-05-08 6:53 ` [Bug middle-end/27409] [4.1 " pinskia at gcc dot gnu dot org 2006-05-09 14:33 ` rguenth at gcc dot gnu dot org 2006-05-09 14:33 ` rguenth at gcc dot gnu dot org 2006-05-15 19:32 ` patchapp at dberlin 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=bug-27409-183@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).