From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: binutils@sourceware.cygnus.com, newlib@sourceware.cygnus.com
Subject: HPPA .subspa
Date: Thu, 07 Oct 1999 05:28:00 -0000 [thread overview]
Message-ID: <37FC98CC.CDD110E7@OARcorp.com> (raw)
I hate to crosspost but this one seems to merit it.
Targets: hppa1.1-elf/hppa1.1-rtems
Version: all newlib versions that I know of including 1.8.2
binutils: OK with 2.9.1, breaks with recent snapshots.
I am trying to test newlib 1.8.2 with late model binutils to get
an RTEMS patch submitted. Earlier this week, I ran into trouble
because the .subspa directive has been removed. At first, I thought
this would just impact RTEMS specific code. A quick find/grep turned
up all of this:
bash$ find newlib-1.8.2 -type f | xargs -e grep -il subspa
newlib-1.8.2/newlib/libc/machine/hppa/DEFS.h
newlib-1.8.2/newlib/libc/machine/hppa/pcc_prefix.s
newlib-1.8.2/newlib/libc/machine/hppa/setjmp.S
newlib-1.8.2/newlib/libc/sys/rtems/crt0.c
newlib-1.8.2/libgloss/hp74x/crt0.s
newlib-1.8.2/libgloss/hp74x/debugger.s
newlib-1.8.2/libgloss/hp74x/iva_table.s
newlib-1.8.2/libgloss/pa/hp-milli.s
newlib-1.8.2/libgloss/pa/setjmp.S
bash$ find newlib-1.8.2 -type f | xargs -e grep -i subspa | wc -l
71
For a total of 71 subspace in 9 files.
I am not an hppa expert, so don't really know how to deal with this
one. RTEMS itself has 34 subspaces in 3 files impacted as well so
advice on how to semi-mechanically correct this would be greatly
appreciated.
Hopefully, this report will spark enough discussion to figure out what
to
do.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
reply other threads:[~1999-10-07 5:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=37FC98CC.CDD110E7@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=binutils@sourceware.cygnus.com \
--cc=newlib@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).