public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: athena@fftw.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/10631: [3.3 regression] ICE in simplify_unary_expr at simplify-rtx.c:387 for easy sse2 code with mode V2DF Date: Mon, 05 May 2003 17:41:00 -0000 [thread overview] Message-ID: <20030505174133.27884.qmail@sources.redhat.com> (raw) Old Synopsis: gcc 3.3 20030428 bug in simplifier for sse2 code New Synopsis: [3.3 regression] ICE in simplify_unary_expr at simplify-rtx.c:387 for easy sse2 code with mode V2DF State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Mon May 5 17:41:33 2003 State-Changed-Why: Confirmed on GCC 3.3 20030503, but it's fixed in GCC 3.4 20030503. Since mode V2DF was introduced with GCC 3.3, I'm not sure this qualifies as a regression, so the PR should be closed. I leave it open in case I'm plain wrong. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10631
reply other threads:[~2003-05-05 17:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030505174133.27884.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=athena@fftw.org \ --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).