public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: ebotcazou@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/7675: [3.2/3.3 regression] ICE in fixup_var_refs_1 Date: Tue, 24 Dec 2002 12:26:00 -0000 [thread overview] Message-ID: <20021224202601.4257.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/7675; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, sowhat@amnis.co.jp, ebotcazou@gcc.gnu.org Cc: Subject: Re: optimization/7675: [3.2/3.3 regression] ICE in fixup_var_refs_1 Date: Tue, 24 Dec 2002 12:24:53 -0800 The regression reported in PR optimization/7675 showed up starting with this patch: 2000-11-11 Jason Merrill <jason@redhat.com> * function.c (assign_parms): If TREE_ADDRESSABLE is set, try to give the parm a register and then call put_var_into_stack. * stmt.c (expand_decl): Likewise. cp/ * typeck.c (mark_addressable): Don't call put_var_into_stack. Here's a small test case that causes the compiler to ICE when compiled on i686-linux with -O: ------------------- /* ICE when compiled with -O */ int dummy (int *); void foo(int i, int j) { int k=j; void bar() { int x=k, y=i, z=j; } dummy(&j); } ------------------- Output from the mainline compiler: 7675.c: In function `foo': 7675.c:9: internal compiler error: in fixup_var_refs_1, at function.c:1900 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Eric, I just noticed that you're working on a patch. Perhaps this information will be useful for you. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7675
next reply other threads:[~2002-12-24 20:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-24 12:26 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-31 0:26 Eric Botcazou 2002-12-03 6:06 ebotcazou
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=20021224202601.4257.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=ebotcazou@gcc.gnu.org \ --cc=gcc-prs@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).