public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/7248: [m68k] broken "inclusive or" code Date: Fri, 14 Mar 2003 16:26:00 -0000 [thread overview] Message-ID: <20030314162600.17186.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 741 bytes --] The following reply was made to PR target/7248; it has been noted by GNATS. From: Andreas Schwab <schwab@suse.de> To: martin@blom.org, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, bangerth@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: target/7248: [m68k] broken "inclusive or" code Date: Fri, 14 Mar 2003 17:22:49 +0100 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. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
next reply other threads:[~2003-03-14 16:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-14 16:26 Andreas Schwab [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-19 10:02 schwab 2003-03-18 10:56 Martin Blom 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=20030314162600.17186.qmail@sources.redhat.com \ --to=schwab@suse.de \ --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).