From: Paul E Murphy <murphyp@linux.ibm.com>
To: GNU C Library <libc-alpha@sourceware.org>
Cc: carlos@redhat.com,
Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Subject: long double redirects and dynamic loader behavior
Date: Mon, 24 Feb 2020 14:10:15 -0600 [thread overview]
Message-ID: <4602467a-2114-34d5-4f99-bf5ac4ef3d6d@linux.ibm.com> (raw)
Tulio mentioned that he and Carlos discussed this topic during Cauldron
last year.
As far as I understand it, dlopen becomes problematic when loading code
compiled against an unknown long double ABI. My understanding is the
gnu-attribute exists to help catch those cases at link time. I am
unsure how, or if it does anything to assist dynamically loaded libraries.
dlsym is more tricky. The redirects obfuscate the naming of many common
symbols. I.e dlsym(...,"printf") might give you something which almost
works, but is broken.
What is the current thinking regarding the behavior of these features
when redirects are used?
next reply other threads:[~2020-02-24 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 20:10 Paul E Murphy [this message]
2020-02-26 2:15 ` long double redirects and dynamic loader behavior Carlos O'Donell
2020-02-26 9:49 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4602467a-2114-34d5-4f99-bf5ac4ef3d6d@linux.ibm.com \
--to=murphyp@linux.ibm.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.ibm.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).