From: Richard Henderson <rth@twiddle.net>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: DSO (dynamic shared objects) support
Date: Tue, 18 Jun 2013 14:40:35 -0700 [thread overview]
Message-ID: <51C0D3D3.5060609@twiddle.net> (raw)
In-Reply-To: <20130618201520.GJ31207@redhat.com>
On 06/18/2013 01:15 PM, Daniel P. Berrange wrote:
> By having all the private symbols change their version tag on every
> release, we make it a total PITA for anyone to provide closed source,
> out of tree, third party modules. Which is nice a feature :-)
Using a symbol version file also means that symbols that aren't
explicitly exported are not present in the dynamic symbol table.
Which isn't *quite* as good as using compiler-level symbol visibility
markup, but the linker can sometimes optimize code sequences in place
or at minimum reduce a full symbol relocation to a relative relocation.
> Symbol versioning like this isn't portable to Windows, but it works
> on Solaris and Linux at least. I'm not sure about BSD support for
> symbol versioning.
Given that symbol versioning is mostly a forward compatible extension
to ELF, assuming the linker doesn't date from the dark ages one should
at least be able to take advantage of visibility improvements, even if
actual symbol versions aren't enforced.
r~
next prev parent reply other threads:[~2013-06-18 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 11:37 [Qemu-devel] RFC: DSO (dynamic shared objects) support Michael Tokarev
2013-06-18 12:05 ` Laszlo Ersek
2013-06-18 13:06 ` Paolo Bonzini
2013-06-18 12:17 ` Laszlo Ersek
2013-06-18 12:19 ` Michael Tokarev
2013-06-18 12:28 ` Michael Tokarev
2013-06-18 20:15 ` Daniel P. Berrange
2013-06-18 21:40 ` Richard Henderson [this message]
2013-06-18 12:42 ` Anthony Liguori
2013-06-18 13:12 ` Peter Maydell
2013-06-18 13:32 ` Paolo Bonzini
2013-06-18 13:13 ` Paolo Bonzini
2013-06-18 20:19 ` Daniel P. Berrange
2013-06-18 21:34 ` Peter Maydell
2013-06-18 19:35 ` Richard Henderson
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=51C0D3D3.5060609@twiddle.net \
--to=rth@twiddle.net \
--cc=berrange@redhat.com \
--cc=lersek@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.