From: Ulrich Drepper <drepper@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Dibyendu Majumdar <mobile@majumdar.org.uk>,
jit@gcc.gnu.org,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Thinking about libgccjit SONAME bump for gcc 5.2 (was Re: Four jit backports to gcc 5 branch)
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <CAOPLpQdX69F2pVbXnC84+d8doSVDN1VZA37i9GBvCbiJd0n3Og@mail.gmail.com> (raw)
In-Reply-To: <1435613171.13727.189.camel@surprise>
On Mon, Jun 29, 2015 at 5:26 PM, David Malcolm <dmalcolm@redhat.com> wrote:
> I'm looking at ways to manage libgccjit API/ABI as per this thread:
> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01982.html
> by transitioning to using symbol versioning, so that the linker can tag
> subsets of libgccjit symbols in both libgccjit and in client binaries.
You don't have to bump the SONAME to introduce symbol versioning.
glibc in the beginning didn't have symbol versioning and we wrote the
linker and dynamic linker support so that no SONAME change was
necessary. The idea is that unversioned symbols are satisfied by the
oldest symbol version.
next prev parent reply other threads:[~2015-06-29 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Four jit backports to gcc 5 branch David Malcolm
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Thinking about libgccjit SONAME bump for gcc 5.2 (was Re: Four jit backports to gcc 5 branch) David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Ulrich Drepper [this message]
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Eight more jit backports to gcc 5 branch David Malcolm
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=CAOPLpQdX69F2pVbXnC84+d8doSVDN1VZA37i9GBvCbiJd0n3Og@mail.gmail.com \
--to=drepper@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
--cc=mobile@majumdar.org.uk \
/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).