From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Pending fixes for all-ABIs builds
Date: Tue, 08 Nov 2016 08:28:00 -0000 [thread overview]
Message-ID: <35e9c513-c873-3d7e-38e4-6aa14e9ef245@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611072319260.23588@digraph.polyomino.org.uk>
On 11/08/2016 12:25 AM, Joseph Myers wrote:
> https://sourceware.org/ml/libc-alpha/2016-11/msg00213.html (Update nios2
> localplt.data)
>
> https://sourceware.org/ml/libc-alpha/2016-11/msg00214.html (Update alpha
> localplt.data)
>
> https://sourceware.org/ml/libc-alpha/2016-11/msg00216.html (Add
> localplt.data for hppa)
>
> https://sourceware.org/ml/libc-alpha/2016-11/msg00217.html (Add
> localplt.data for sh)
I looked at those and they seemed reasonable to me.
But there's one pre-existing issue I've been wondering about for a while
(along with the s390 maintainers): I don't understand why we have PLT
references to malloc & friends in ld.so. The malloc implementation
there is not compliant with the C requirements. Why is it exported, and
why do we use GOT indirection to call it?
Florian
next prev parent reply other threads:[~2016-11-08 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 23:25 Joseph Myers
2016-11-08 8:28 ` Florian Weimer [this message]
2016-11-08 23:22 ` Joseph Myers
2016-11-09 8:14 ` Florian Weimer
2016-11-09 8:18 ` Joseph Myers
2016-11-09 9:01 ` Andreas Schwab
2016-11-09 11:56 ` Florian Weimer
2016-11-09 13:26 ` Andreas Schwab
2016-11-09 13:39 ` Florian Weimer
2016-11-09 13:47 ` Andreas Schwab
2016-11-09 13:52 ` Florian Weimer
2016-11-09 14:50 ` Andreas Schwab
2016-11-09 14:54 ` Florian Weimer
2016-11-09 22:00 ` Roland McGrath
2016-11-10 7:58 ` Florian Weimer
2016-11-10 9:28 ` Andreas Schwab
2016-11-10 16:30 ` _rtld_global_ro and static dlopen (was: Re: Pending fixes for all-ABIs builds) Florian Weimer
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=35e9c513-c873-3d7e-38e4-6aa14e9ef245@redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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).