From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: binutils@sources.redhat.com
Subject: RFC on removing R_PARISC_DIR21L in DSO for hppa?
Date: Sun, 27 Jun 2004 15:39:00 -0000 [thread overview]
Message-ID: <20040627153936.GF18912@baldric.uwo.ca> (raw)
I'm seeing that on occassion a number of DSO's have ended up with
R_PARISC_DIR21L relocations, these relocations are not handled by the
dyanmic loader in glibc (I'm not sure how to handle them to tell you the
truth). There is code here that is '#ifdef 0' with a comment indicating
that it is for debugging purposes.
I assumed that DIR21L and such relocations would endup as DIR32
relocations, those being the only relocs I've ever seen in after a final
link. Would it be valid to warn again when DIR21L relocations are about
to make it into the final link? Or am I missing the point here, do they
finally get turned into DIR32 and halting the link in
elf32_hppa_check_relocs() is not the correct thing to do?
Cheers,
Carlos
next reply other threads:[~2004-06-27 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 15:39 Carlos O'Donell [this message]
2004-06-27 23:45 ` Alan Modra
2004-06-28 17:54 ` Carlos O'Donell
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=20040627153936.GF18912@baldric.uwo.ca \
--to=carlos@baldric.uwo.ca \
--cc=binutils@sources.redhat.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).