From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Progress since 1.1.9
Date: Thu, 28 May 2015 13:45:15 +0200 [thread overview]
Message-ID: <20150528114437.GK20259@port70.net> (raw)
In-Reply-To: <20150527231308.GA10123@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2015-05-27 19:13:08 -0400]:
> The one roadmap item I don't have any progress on is what to do with
> the libgcc_s symbol version mess, and I think we should probably just
> hold off until the next release cycle for that now.
in case anyone wonders about the issue:
libgcc_s has a symbolic reference to an internal deprecated
symbol with no default version on x86 (in gcc trunk).
(so no @version only @@version which makes it invisible to
musl and ld).
the deprecated function is a constructor in libgcc_s that
initializes an unused struct in libgcc_s.
the only reason the symbol got versioned this way is because
they want old binaries to work and remove the symbol from
libgcc_s for new binaries, while still using the same symbol
name in new binaries but with different abi behaviour: now
it's only available in libgcc.a to fix their ifunc hack for
multi-versioning.
since it's a symbol internal to libgcc and the semantics
of the symbol changed they could have just used a new name
and left the old one alone (so old stuff is guaranteed to not
break including musl and new binaries use the new symbol with
new semantics).
so i still think my proposed libgcc patch makes more sense
than versioning:
https://gcc.gnu.org/ml/gcc-patches/2015-05/msg00899.html
gcc is unlikely to fix this, but this is a nonsense usecase
(and there is no other known use of versioning that is broken
with musl.. in theory other libs may deprecate symbols in a
similar way while still keeping symbolic references to them,
but such use was not yet observed).
in musl-gcc it can be worked around by preloading a noop
__cpu_indicator_init and in a musl based gcc it can be
patched out.
next prev parent reply other threads:[~2015-05-28 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 23:13 Rich Felker
2015-05-28 11:45 ` Szabolcs Nagy [this message]
2015-05-28 17:12 ` Rich Felker
2015-05-28 19:47 ` Szabolcs Nagy
2015-05-28 20:43 ` Rich Felker
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=20150528114437.GK20259@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).