From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFT] final cur of tr based current for -ac8
Date: 11 Nov 2001 18:21:37 -0800 [thread overview]
Message-ID: <9snbnh$dg6$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011110173331.F17437@redhat.com> <Pine.LNX.4.33.0111111119270.305-100000@mikeg.weiden.de> <20011111190114.A31746@redhat.com>
Followup to: <20011111190114.A31746@redhat.com>
By author: Benjamin LaHaise <bcrl@redhat.com>
In newsgroup: linux.dev.kernel
>
> On Sun, Nov 11, 2001 at 11:58:30AM +0100, Mike Galbraith wrote:
> > The below seems to make flogging noises, but is likely too soggy.
>
> Erk, the behaviour of str with your patch isn't quite compatible
> enough for a smooth transition. What is really needed is to have
> "str" error out or generate the existing strl with a huge warning
> about unspecified type. Either way the kernel has to work with
> both old and new tools for a brief period of time.
>
The current behaviour is a bug, plain and simple. The only way to
make backwards-compatible behaviour is to make "strl %eax" and "strw
%ax" behave properly while "str %ax" really does an "strl %eax" (the
current, broken, behaviour.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2001-11-12 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 19:14 [RFT] final cur of tr based current for -ac8 Benjamin LaHaise
2001-11-10 20:33 ` John Levon
2001-11-10 22:33 ` Benjamin LaHaise
2001-11-10 22:54 ` Keith Owens
2001-11-11 0:39 ` Benjamin LaHaise
2001-11-11 1:48 ` John Levon
2001-11-11 10:58 ` Mike Galbraith
2001-11-12 0:01 ` Benjamin LaHaise
2001-11-12 2:21 ` H. Peter Anvin [this message]
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='9snbnh$dg6$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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: 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