From: Matthew Wilcox <willy@debian.org>
To: LaMont Jones <lamont@hp.com>
Cc: Matthew Wilcox <willy@debian.org>,
binutils@sources.redhat.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] second sr0 patch
Date: Sun, 23 Feb 2003 22:27:48 +0000 [thread overview]
Message-ID: <20030223222748.F2938@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030223222035.26E3812133@security.hp.com>; from lamont@hp.com on Sun, Feb 23, 2003 at 03:20:35PM -0700
On Sun, Feb 23, 2003 at 03:20:35PM -0700, LaMont Jones wrote:
> In article <20030223204842.E2938@parcelfarce.linux.theplanet.co.uk> you wrote:
> > +++ gas/config/tc-hppa.c 23 Feb 2003 19:21:09 -0000
> > @@ -1794,7 +1794,7 @@ pa_ip (str)
> > if (!pa_parse_number (&s, 0))
> > break;
> > num = pa_number;
> > - CHECK_FIELD (num, 3, 0, 1);
> > + CHECK_FIELD (num, 3, 1, 1);
> I don't think this is a good plan. Emit a warning, sure, but there is
> a large collection of legacy PARISC assembly code out there that has
> this perfectly legal, and hp-ux assembler-accepted-from-day-0 construct.
OK, patch withdrawn. It's misleading to use this construct, but if people
have been doing it for fifteen years then it's just not reasonable to
not support it now.
The other patch still stands; we're not using sr0 so it's misleading to
pretend that we are.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-02-23 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 20:48 [parisc-linux] second sr0 patch Matthew Wilcox
2003-02-23 22:20 ` LaMont Jones
2003-02-23 22:27 ` Matthew Wilcox
2003-02-23 22:27 ` Matthew Wilcox [this message]
2003-02-23 22:20 ` LaMont Jones
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=20030223222748.F2938@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=binutils@sources.redhat.com \
--cc=lamont@hp.com \
--cc=parisc-linux@lists.parisc-linux.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