From: <joel@OARcorp.com>
To: binutils@sourceware.cygnus.com
Subject: RTEMS Patch for binutils 2.9.1
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9905130814160.28683-200000@oar3remote> (raw)
I do not know if I have submitted the individual patches in this in the
past or not. I wanted to make sure that it got in though. The patch
applied without hassle to binutils-2.9.1.0.14 so I doubt they are in.
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.
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.
Thu May 13 07:31:58 CDT 1999 Joel Sherrill (joel@OARcorp.com)
* bfd/config.bfd (i[3456]86*-*-rtems*, m68k*-*-rtems*): Added to
list of target formats (targ_selvecs).
* bfd/config.bfd (i[3456]86*-*-rtemself*, mips*el-*-rtems*,
powerpcle*-*rtems*, sh-*-rtemself*): New targets.
* gas/configure (i386-*-rtemself*, sh-*-rtemself*): New targets.
* gas/configure.in (i386-*-rtemself*, sh-*-rtemself*): New
targets.
* opcode/hppa.h: Added 72000 instructions.
* ld/configure.tgt (i386-*-rtemself*, sh-*-rtemself*,
mips*el-*-rtems*, powerpcle-*-rtems*): New targets.
next 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 [this message]
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
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.9905130814160.28683-200000@oar3remote \
--to=joel@oarcorp.com \
--cc=binutils@sourceware.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).