From: Daniel Jacobowitz <drow@false.org>
To: Mike Hearn <mike@plan99.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Symbol versions for inlined symbols
Date: Sun, 31 Jul 2005 04:57:00 -0000 [thread overview]
Message-ID: <20050731045749.GA17880@nevyn.them.org> (raw)
In-Reply-To: <pan.2005.07.30.20.33.45.126163@plan99.net>
On Sat, Jul 30, 2005 at 09:33:45PM +0100, Mike Hearn wrote:
> Hi,
>
> One problem with the parallel C++ ABI versioning (which makes it not so
> useful) is that symbols in the libstdc++ namespaces are put into the
> generated binary if you use the STL. Those generated symbols are *not*
> symbol versioned so conflicts can still occur.
You may wish to read the proceedings from this year's GCC summit, where
another solution was presented by some gentlemen from Intel. For
various reasons, symbol versioning is not a useful solution to this
problem.
No one objected to their solution in principle, AFAICT, although there
was some discussion afterwards about whether the use of strong
namespace using was really necessary. I'm afraid I don't understand
C++ well enough to explain the rest of that conversation.
May just need someone to do the work.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-31 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 23:00 Mike Hearn
2005-07-31 4:57 ` Daniel Jacobowitz [this message]
2005-07-31 13:52 ` Mike Hearn
2005-07-31 15:34 ` Daniel Jacobowitz
2005-07-31 6:04 dank
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=20050731045749.GA17880@nevyn.them.org \
--to=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=mike@plan99.net \
/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).