public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: rearnsha@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8896: '-mcpu=xscale -fno-strict-aliasing -O2' generates wrong code Date: Sat, 22 Mar 2003 13:36:00 -0000 [thread overview] Message-ID: <20030322133601.15555.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8896; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: Richard.Earnshaw@arm.com Cc: steven@gcc.gnu.org, enrico.scholz@informatik.tu-chemnitz.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rearnsha@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/8896: '-mcpu=xscale -fno-strict-aliasing -O2' generates wrong code Date: 22 Mar 2003 14:33:14 +0100 Op za 22-03-2003, om 14:28 schreef Richard Earnshaw: > > Synopsis: '-mcpu=xscale -fno-strict-aliasing -O2' generates wrong code > > > > State-Changed-From-To: analyzed->closed > > State-Changed-By: steven > > State-Changed-When: Sat Mar 22 10:05:37 2003 > > State-Changed-Why: > > Fixed according to reporter. Richard Earnshaw posted a patch for this months ago -- apparently without mentioning the PR in the ChangeLog. > > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8896 > > That's 'cos I never got around to committing the patch... > > R. Ah, that explains why I couldn't find the PR in the ChangeLog. Should I re-open the PR? Greetz Steven
next reply other threads:[~2003-03-22 13:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-22 13:36 Steven Bosscher [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-15 18:46 Daniel Jacobowitz 2003-05-14 17:46 Dara Hazeghi 2003-03-22 13:54 steven 2003-03-22 13:36 Richard Earnshaw 2003-03-22 10:05 steven 2002-12-16 10:06 Enrico Scholz 2002-12-12 7:16 Richard Earnshaw 2002-12-12 7:03 rearnsha 2002-12-11 9:57 rearnsha 2002-12-10 15:46 enrico.scholz
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=20030322133601.15555.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --cc=gcc-prs@gcc.gnu.org \ --cc=rearnsha@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).