From: <joel@OARcorp.com>
To: law@cygnus.com
Cc: Richard Henderson <rth@cygnus.com>, binutils@sourceware.cygnus.com
Subject: Re: RTEMS Patch for binutils 2.9.1
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9905140710490.3920-100000@oar3remote> (raw)
In-Reply-To: <485.926656529@upchuck.cygnus.com>
On Thu, 13 May 1999, Jeffrey A Law wrote:
>
> In message < Pine.LNX.4.10.9905131237110.501-100000@oar3remote >you write:
> > My understanding was that these were pretty critical instructions for an
> > OS implementation. Doesn't one of the other open-source OSes have a need
> > for these as well?
> Not really. The only ones I ever would have found useful would be movement
> to/from the shadow regs. Hmmm, actually we may have had an assembler macro
> to create mtcpu/mfcpu instructions using .word directives. It's hard to
> remember since I haven't done PA OS work in a while.
I recall using a similar trick initially with the RTEMS PA port and then
we decided it was ugly and error prone. It was easier to simply add the
instructions to gas. :)
--joel
prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 joel
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` joel
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` joel [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=Pine.LNX.4.10.9905140710490.3920-100000@oar3remote \
--to=joel@oarcorp.com \
--cc=binutils@sourceware.cygnus.com \
--cc=law@cygnus.com \
--cc=rth@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).