public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, p.van-hoof@qub.ac.uk, rakdver@gcc.gnu.org Subject: Re: optimization/10312: [3.4 regression] [sparc] optimizer creates wrong code for loop Date: Fri, 04 Apr 2003 22:02:00 -0000 [thread overview] Message-ID: <20030404220219.14419.qmail@sources.redhat.com> (raw) Synopsis: [3.4 regression] [sparc] optimizer creates wrong code for loop Responsible-Changed-From-To: unassigned->rakdver Responsible-Changed-By: ebotcazou Responsible-Changed-When: Fri Apr 4 22:02:19 2003 Responsible-Changed-Why: Your store motion rewrite. State-Changed-From-To: feedback->analyzed State-Changed-By: ebotcazou State-Changed-When: Fri Apr 4 22:02:19 2003 State-Changed-Why: Confirmed as a store motion bug. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10312
reply other threads:[~2003-04-04 22:02 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=20030404220219.14419.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=p.van-hoof@qub.ac.uk \ --cc=rakdver@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).