From: u-uy74@aetey.se
To: musl@lists.openwall.com
Subject: Re: ABI compatibility between versions
Date: Tue, 26 Feb 2019 12:55:12 +0100 [thread overview]
Message-ID: <20190226115512.GJ22812@example.net> (raw)
In-Reply-To: <20190226095837.GC21289@port70.net>
On Tue, Feb 26, 2019 at 10:58:38AM +0100, Szabolcs Nagy wrote:
> other than the bug compatibility, a difference between the
> two approaches is that glibc may do certain abi breaking
> changes while keeping old binaries work, that musl cant do.
I feel this statement is unfair to musl.
AFAICS symbol versioning does not allow "breaking" the ABI, but
*extending* it with new entry points (made to look like the old ones in
the API, which makes the old ones inaccessible via the API).
This is also exactly what musl can do, extend the ABI.
The difference is how to reflect those changes in the API.
Keeping the old API on top of a subset of the occasionally extended ABI
is what glibc does and musl does not.
Regarding old binaries API stability is irrelevant.
Rune
prev parent reply other threads:[~2019-02-26 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 23:18 Alexander Revin
2019-02-26 0:33 ` Rich Felker
2019-02-26 9:58 ` Szabolcs Nagy
2019-02-26 11:28 ` Alexander Revin
2019-02-26 15:11 ` Rich Felker
2019-02-26 16:22 ` Alexander Revin
2019-02-26 11:55 ` u-uy74 [this message]
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=20190226115512.GJ22812@example.net \
--to=u-uy74@aetey.se \
--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).