public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/7595: [m68k] store in global register variable improperly eliminated Date: Tue, 13 May 2003 12:16:00 -0000 [thread overview] Message-ID: <20030513121601.13540.qmail@sources.redhat.com> (raw) The following reply was made to PR target/7595; it has been noted by GNATS. From: Richard Zidlicky <rz@linux-m68k.org> To: Dara Hazeghi <dhazeghi@yahoo.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/7595: [m68k] store in global register variable improperly eliminated Date: Tue, 13 May 2003 13:55:13 +0200 On Sat, May 10, 2003 at 01:23:19AM -0700, Dara Hazeghi wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=7595 > > Hello, > > can you please confirm whether this bug is in a more current gcc (ie > 3.2.3 or 3.3 prerelease)? This report is essentially duplicate to 7871, see http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7871 I have resubmitted it with an improved (architecture independent) testcase and some new information after it was idle for considerable time and a new major gcc version appeared. Apparently I failed to make the reference to the older bug, sorry for that. Meanwhile Jim Wilson has done some progress with 7871. Richard
next reply other threads:[~2003-05-13 12:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-13 12:16 Richard Zidlicky [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:41 giovannibajo 2003-05-14 4:26 Dara Hazeghi 2003-05-12 11:46 giovannibajo 2003-05-10 8:36 Dara Hazeghi
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=20030513121601.13540.qmail@sources.redhat.com \ --to=rz@linux-m68k.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).