public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: ebuddington@wesleyan.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: middle-end/8808: [3.2/3.3 regression] Internal compiler error in extract_constrain_insn_cached Date: Wed, 04 Dec 2002 13:40:00 -0000 [thread overview] Message-ID: <20021204214005.10742.qmail@sources.redhat.com> (raw) Old Synopsis: Internal compiler error in extract_constrain_insn_cached New Synopsis: [3.2/3.3 regression] Internal compiler error in extract_constrain_insn_cached State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Wed Dec 4 13:40:03 2002 State-Changed-Why: Confirmed. Here's a much smaller testcase: ------------------------------- void f(unsigned long long int); void g () { register unsigned long long int i asm ("mm0"); f(i); } ------------------------- It ICEs with both 3.2 and 3.3 branches. It is a regression w.r.t. 3.0. With the above code, the crash happens with both the C and C++ front ends, so I change the category to middle-end. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8808
next reply other threads:[~2002-12-04 21:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-04 13:40 bangerth [this message] 2002-12-18 14:16 Janis Johnson
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=20021204214005.10742.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=ebuddington@wesleyan.edu \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).