From: Andreas Schwab <schwab@suse.de>
To: Gunther Nikl <gni@gecko.de>
Cc: Gunnar Von Boehn <gunnar@genesi-usa.com>, gcc-patches@gcc.gnu.org
Subject: Re: Fix for GCC Bugzilla Bug 36133
Date: Fri, 27 Jun 2008 13:48:00 -0000 [thread overview]
Message-ID: <jehcbfatcv.fsf@sykes.suse.de> (raw)
In-Reply-To: <4864E448.2080204@gecko.de> (Gunther Nikl's message of "Fri, 27 Jun 2008 14:59:52 +0200")
Gunther Nikl <gni@gecko.de> writes:
> Andreas Schwab wrote:
>> "Gunnar Von Boehn" <gunnar@genesi-usa.com> writes:
>>
>>> AFAIK GCC 2.9 did behave correctly in this matter.
>>
>> I don't know what gcc 2.9 refers to, but the handling of lshiftr in
>
> That quite likely refers to GCC 2.95.x
>
>> notice_update_cc was changed 5 years ago, presumably because of a
>> wrong-code bug (I cannot find any reference in the gcc-patches archive).
>
> The following link should be the thread about that change you were
> looking for: http://gcc.gnu.org/ml/gcc/2003-10/msg01236.html
Thanks. That's exactly the test case I was look for.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-06-27 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 13:33 Gunnar Von Boehn
2008-06-17 12:33 ` Andreas Schwab
2008-06-17 17:31 ` Gunnar Von Boehn
2008-06-17 19:21 ` Andreas Schwab
2008-06-19 12:50 ` Gunnar Von Boehn
2008-06-24 16:15 ` Gunnar Von Boehn
2008-06-25 19:05 ` Andreas Schwab
2008-06-27 13:02 ` Gunther Nikl
2008-06-27 13:48 ` Andreas Schwab [this message]
[not found] ` <b989d750806300851s6ff51ad3j4d8b3e6da6fe2599@mail.gmail.com>
2008-07-01 9:03 ` Fwd: " Gunnar Von Boehn
2008-06-27 13:57 ` Andreas Krebbel
2008-06-27 14:12 ` Andreas Schwab
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=jehcbfatcv.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=gunnar@genesi-usa.com \
/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: link
Be 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).