From: <joel@OARcorp.com>
To: Richard Henderson <rth@cygnus.com>
Cc: binutils@sourceware.cygnus.com, "Jeffrey A. Law" <law@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.9905131237110.501-100000@oar3remote> (raw)
In-Reply-To: <19990513095246.A28238@cygnus.com>
On Thu, 13 May 1999, Richard Henderson wrote:
> On Thu, May 13, 1999 at 08:43:30AM -0500, joel@OARcorp.com wrote:
> > This patch does a few minor things for RTEMS targets mostly in
> > configuration files. It also adds some RTEMS targets that are
> > either aliases or copies of existing targets with no new files.
>
> These bits applied.
>
> > Included in this patch is one thing I am pretty sure will be rejected.
> > The mod to opcode/hppa.h adds instructions and unless something has
> > changed recently, knowing that these instructions exist requires having
> > access to a manual that was restricted in some way. Perhaps one of the
> > HPPA folks will be able to state something more recent HPPA technical
> > information.
>
> Jeff, can I leave this bit to you?
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?
>
> * opcode/hppa.h: Added 72000 instructions.
>
> *** /usr1/rtems/work/original/binutils-2.9.1/include/opcode/hppa.h Fri May 1 10:48:35 1998
> --- binutils-2.9.1/include/opcode/hppa.h Mon Jan 25 15:16:47 1999
> ***************
> *** 370,375 ****
> --- 370,383 ----
> { "fice", 0x040002c0, 0xfc001fdf, "Zx(b)", pa10},
> { "diag", 0x14000000, 0xfc000000, "D", pa10},
>
> + /* Following group is 72000 specific */
> + { "mtcpu", 0x14001600, 0xfc00ffff, "x,^"},
> + { "mfcpu", 0x14001A00, 0xfc00ffff, "^,x"},
> + { "tocen", 0x14403600, 0xffffffff, ""},
> + { "tocdis", 0x14401620, 0xffffffff, ""},
> + { "shdwgr", 0x14402600, 0xffffffff, ""},
> + { "grshdw", 0x14400620, 0xffffffff, ""},
> +
> /* gfw and gfr are not in the HP PA 1.1 manual, but they are in either
> the Timex FPU or the Mustang ERS (not sure which) manual. */
> { "gfw", 0x04001680, 0xfc003fdf, "Zx(s,b)", pa11},
>
next 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 [this message]
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` joel
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.9905131237110.501-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).