public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Martin Blom <martin@blom.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/7248: [m68k] broken "inclusive or" code Date: Tue, 18 Mar 2003 10:56:00 -0000 [thread overview] Message-ID: <20030318105601.25174.qmail@sources.redhat.com> (raw) The following reply was made to PR target/7248; it has been noted by GNATS. From: Martin Blom <martin@blom.org> To: Andreas Schwab <schwab@suse.de> Cc: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <bangerth@gcc.gnu.org>, <gcc-prs@gcc.gnu.org> Subject: Re: target/7248: [m68k] broken "inclusive or" code Date: Tue, 18 Mar 2003 11:50:13 +0100 (CET) | On 14 Jan 2003 bangerth@dealii.org wrote: | | Old Synopsis: gcc 2.95.3 for m68k generates broken "inclusive or" code | New Synopsis: [m68k] broken "inclusive or" code | | State-Changed-From-To: open->feedback | State-Changed-By: bangerth | State-Changed-When: Tue Jan 14 13:38:55 2003 | State-Changed-Why: | Your fix has been applied already sometime back in 1997. Do | you have the chance to test the problem with some newer | version of gcc? gcc2.95.x is no longer maintained. On Fri, 14 Mar 2003, Andreas Schwab wrote: > I can still reproduce the bug with gcc 3.4 as of today. The included > patch is still needed. There are no changes around this place since the > file was imported into CVS. Hi Andreas and the rest ... That's what I thought when I looked in the CVS before reporting the bug. Unfortunately, I've not yet been able to verify it myself by actually running a test program built with gcc 3.x for m68k (because of, well, "lack of time" and lack of a system able to run gcc 3.x for m68k). Sorry about that. -- ---- Martin Blom --------------------------- martin@blom.org ---- Eccl 1:18 http://martin.blom.org/
next reply other threads:[~2003-03-18 10:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-18 10:56 Martin Blom [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-19 10:02 schwab 2003-03-14 16:26 Andreas Schwab 2003-01-14 21:38 bangerth
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=20030318105601.25174.qmail@sources.redhat.com \ --to=martin@blom.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).