From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix ppc32 dl-machine.h
Date: Wed, 26 Mar 2003 12:12:00 -0000 [thread overview]
Message-ID: <200303260713.h2Q7DDZ28063@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Tuesday, 25 March 2003 11:40:55 +0100 <20030325114055.C1717@sunsite.ms.mff.cuni.cz>
> It seems the 2003-03-02 cleanups broke relocs against local symbols on ppc32
> (e.g. a bunch of binutils tests now fail).
> On ppc32 (and sparc32) for those relocs r_addend already includes st_value,
> so ATM glibc adds them in twice.
I can't find anything in the ABI spec to suggest this should be done. Is
it considered part of the spec, or a binutils bug that we are just stuck with?
I had the impression that this was a sparc-specific bug, not the specified
behavior. Do other Rela platforms use this meaning?
Thanks,
Roland
next prev parent reply other threads:[~2003-03-26 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 13:52 Jakub Jelinek
2003-03-25 17:30 ` Jakub Jelinek
2003-03-26 12:12 ` Roland McGrath [this message]
2003-03-28 2:47 ` Roland McGrath
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=200303260713.h2Q7DDZ28063@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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).