From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: alan@linuxcare.com.au (Alan Modra)
Cc: binutils@sourceware.cygnus.com, dhd@linuxcare.com
Subject: Re: gas 2.10.91 from 20000920 cvs is broken under hpux 10.20
Date: Sat, 23 Sep 2000 09:49:00 -0000 [thread overview]
Message-ID: <200009231648.MAA12936@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <Pine.LNX.4.21.0009231958340.6889-100000@front.linuxcare.com.au>
> Thanks. I'll commit the change, which goes back to the old SOM handling
> for external and weak syms, on the strength of your say-so. Incidentally,
> dhd's original patch was surrounded with #ifdef OBJ_ELF, but I changed
> it...
Regarding the #ifdef OBJ_ELF, if it was in as per dhd's original patch,
would this work for --enable-targets=all?
Another question. The HP linker has a -O option which eliminates
unnecessary addil's (and also dead procedures). Could this upset
the relative branches built by the assembler if one of the eliminated
addil's was between the branch and target?
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2000-09-23 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200009230838.EAA06201@hiauly1.hia.nrc.ca>
2000-09-23 2:59 ` Alan Modra
2000-09-23 9:49 ` John David Anglin [this message]
2000-09-23 20:53 ` Alan Modra
2000-09-24 6:20 ` Jeffrey A Law
2000-09-24 9:51 ` John David Anglin
2000-09-25 8:27 ` Jeffrey A Law
2000-09-25 8:53 ` John David Anglin
2000-09-24 10:53 ` John David Anglin
2000-09-24 21:25 ` Alan Modra
2000-09-25 9:08 ` John David Anglin
2000-09-24 13:05 ` John David Anglin
2000-09-24 21:55 ` Alan Modra
[not found] <no.id>
2000-09-22 16:56 ` John David Anglin
2000-09-22 18:49 ` Alan Modra
2000-09-22 22:42 ` John David Anglin
2000-09-22 23:11 ` Alan Modra
2000-09-22 16:39 John David Anglin
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=200009231648.MAA12936@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=dhd@linuxcare.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).