From: Jakub Jelinek <jakub@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Szabolcs Nagy <nsz@port70.net>, "H.J. Lu" <hjl.tools@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>,
Mike Stump <mikestump@comcast.net>,
Jack Howarth <howarth.at.gcc@gmail.com>,
Ian Lance Taylor <ian@airs.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Iain Sandoe <iain@codesourcery.com>,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Rich Felker <dalias@libc.org>
Subject: Re: PATCH] PR target/65612: Multiversioning doesn't work with DSO nor PIE
Date: Mon, 11 May 2015 13:05:00 -0000 [thread overview]
Message-ID: <20150511130523.GX1751@tucnak.redhat.com> (raw)
In-Reply-To: <5550A2F5.50603@arm.com>
On Mon, May 11, 2015 at 01:39:17PM +0100, Szabolcs Nagy wrote:
> fyi, musl loader loads libstdc++ just fine because it has no
But will it load any shared library that uses any of the 26 (if I count well
on x86_64) @ symbols from libstdc++.so.6?
readelf -Ws /lib64/libstdc++.so.6 | grep '@' | grep -v 'UND\|@@'
For libstdc++ that is primarily C++ apps and shared libraries
compiled/linked with GCC 4.0.0.
> musl may end up supporting @version but that's an independent
> quest.
It is not independent. If musl claims to support symbol versioning, it
should support it properly, if not, then supposedly gcc configured for musl
can't be compatible with gcc configured for other linux C libraries, and
should force symbol versioning off.
Jakub
next prev parent reply other threads:[~2015-05-11 13:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 2:25 H.J. Lu
2015-03-30 2:34 ` H.J. Lu
2015-03-30 2:40 ` H.J. Lu
2015-03-30 22:26 ` H.J. Lu
2015-03-31 0:54 ` Jack Howarth
2015-03-31 2:08 ` H.J. Lu
2015-03-31 2:42 ` H.J. Lu
2015-03-31 3:14 ` Jack Howarth
2015-03-31 3:09 ` Jack Howarth
2015-03-31 4:04 ` H.J. Lu
2015-03-31 5:39 ` Jakub Jelinek
2015-03-31 6:20 ` Rainer Orth
2015-03-31 10:39 ` H.J. Lu
2015-03-31 14:25 ` Jack Howarth
2015-03-31 15:58 ` H.J. Lu
2015-03-31 16:10 ` Jack Howarth
2015-03-31 16:15 ` H.J. Lu
2015-03-31 16:39 ` Jack Howarth
2015-03-31 17:00 ` H.J. Lu
2015-03-31 18:33 ` Jack Howarth
2015-04-14 15:07 ` H.J. Lu
2015-04-16 16:29 ` Mike Stump
2015-04-17 8:05 ` Uros Bizjak
2015-04-17 10:36 ` H.J. Lu
2015-04-17 11:04 ` Uros Bizjak
2015-04-17 11:12 ` Uros Bizjak
2015-04-17 11:38 ` Jakub Jelinek
2015-04-17 11:48 ` H.J. Lu
2015-04-17 12:00 ` Jakub Jelinek
2015-04-17 12:36 ` H.J. Lu
2015-04-17 12:40 ` Jakub Jelinek
2015-05-08 23:00 ` Rich Felker
2015-05-08 23:59 ` H.J. Lu
2015-05-09 14:31 ` Szabolcs Nagy
2015-05-09 17:41 ` H.J. Lu
2015-05-09 18:57 ` Szabolcs Nagy
2015-05-11 10:20 ` Szabolcs Nagy
2015-05-11 10:32 ` Jakub Jelinek
2015-05-11 12:39 ` Szabolcs Nagy
2015-05-11 13:05 ` Jakub Jelinek [this message]
2015-05-11 15:30 ` Szabolcs Nagy
2015-05-11 14:12 ` Rich Felker
2015-05-09 19:36 ` Rich Felker
2015-05-09 19:54 ` Jakub Jelinek
2015-07-22 21:14 ` Sriraman Tallam
2015-04-17 12:23 ` Mike Stump
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=20150511130523.GX1751@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=dalias@libc.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=howarth.at.gcc@gmail.com \
--cc=iain@codesourcery.com \
--cc=ian@airs.com \
--cc=mikestump@comcast.net \
--cc=nsz@port70.net \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=szabolcs.nagy@arm.com \
--cc=ubizjak@gmail.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).