From: "Jerry Quinn" <jquinn@nortelnetworks.com>
To: law@cygnus.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: PATCH: add pa2.0 system instructions
Date: Wed, 07 Jul 1999 14:21:00 -0000 [thread overview]
Message-ID: <14211.50168.462241.720881@gargle.gargle.HOWL> (raw)
In-Reply-To: <14149.931327124@upchuck.cygnus.com>
>> "jeff" == Jeffrey A Law <law@cygnus.com> writes:
jeff> In message < 14209.5087.709459.591226@gargle.gargle.HOWL >you write:
>> I mostly started playing to get in the extra opcodes for long displacement
>> float load/store but started to look at completing the pa2.0 support. So
>> I added the easy (!) stuff first.
jeff> Certainly the way to go. I started with the easy stuff too ;-) The
jeff> load/store support is some of the ugliest stuff in the new PA2.0
jeff> support. I'm hoping you did a cleaner job than I so that I can toss my
jeff> code in favor of yours instead of trying to rewrite mine.
I only have a bit of it already implemented, mostly because I wasn't sure
about the best way to proceed in terms of codes. But I'm willing to keep
working on it :-)
One thing I think will make things easier is the float code renaming I had
originally tried to submit. I tried to count up the cases where we would need
new codes and I don't think there are enough single letters left to do the job
well. Renaming the float codes will give us a significant amount of extra
room.
The best situation would allow us to include some of the completers in the
opcode name itself, but I don't see how that will work easily.
jeff> My plan is to clean up and contribute the stuff I did (that you haven't
jeff> already done) starting in mid July. At the same time my development
jeff> focus is shifting to PA64 support (which will in turn stress the PA2.0
jeff> support).
jeff> I'll also be contributing gcc changes to support the new assembler
jeff> syntax, so there's no need to work on that, except from a testing
jeff> standpoint.
Are you making the new syntax active in gas at all levels or just 2.0?
jeff> jeff
Jerry
--
Jerry Quinn Tel: (514) 761-8737
jquinn@nortelnetworks.com Fax: (514) 761-8505
Speech Recognition Research
next prev parent reply other threads:[~1999-07-07 14:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Jerry Quinn
1999-07-01 0:00 ` Jeffrey A Law
1999-07-05 13:22 ` Jerry Quinn
1999-07-06 23:00 ` Jeffrey A Law
1999-07-07 14:21 ` Jerry Quinn [this message]
1999-07-08 12:58 ` Jeffrey A Law
1999-07-08 14:07 ` Jerry Quinn
1999-07-08 22:37 ` Jeffrey A Law
1999-07-09 8:02 ` Jerry Quinn
1999-07-08 14:55 ` Jerry Quinn
1999-07-08 22:27 ` Jeffrey A Law
1999-07-09 6:35 ` Jerry Quinn
1999-07-09 9:34 ` Jeffrey A Law
1999-07-09 10:17 ` Jerry Quinn
1999-07-09 10:44 ` Jeffrey A Law
1999-07-13 13:26 ` Jerry Quinn
-- strict thread matches above, loose matches on Subject: below --
1999-07-01 0:00 Jerry Quinn
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=14211.50168.462241.720881@gargle.gargle.HOWL \
--to=jquinn@nortelnetworks.com \
--cc=binutils@sourceware.cygnus.com \
--cc=law@cygnus.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).