public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cristipp at excite dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/21405] Template inlines have global visibility
Date: Mon, 20 Mar 2006 17:07:00 -0000 [thread overview]
Message-ID: <20060320170738.7539.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21405-10578@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from cristipp at excite dot com 2006-03-20 17:07 -------
(In reply to comment #11)
> There is an one defintion rule in C++ unlike most other languages which have
> weak symbols. And if you are working around it by using hidden symbols well
> you are asking to run into troubles.
I don't believe that C++ has to say (should say) anything that pertains to
shared libraries. Moreover, symbol versions were added as workarounds for
problems created by the ELF format semantics. This is a platform specific
problem, not a pure C++ problem. However, to have the gnu toolchain to properly
support C++ on ELF platforms, adding proper versioning for *all* symbols,
including template-originated symbols is a must. I'm not sure if this is a task
for g++ of for the linker or for both, but someone should eventually
acknowledge that there is a problem and start looking for solutions...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21405
next prev parent reply other threads:[~2006-03-20 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21405-10578@http.gcc.gnu.org/bugzilla/>
2005-12-30 18:20 ` pinskia at gcc dot gnu dot org
2006-03-20 17:07 ` cristipp at excite dot com [this message]
2006-03-20 17:30 ` hjl at lucon dot org
2006-03-20 18:32 ` cristipp at excite dot com
2006-03-20 19:34 ` pluto at agmk dot net
2006-03-20 19:35 ` pluto at agmk dot net
2006-03-22 4:51 ` bkoz at gcc dot gnu dot org
2006-03-22 19:11 ` cristipp at excite dot com
2006-06-20 18:14 ` [Bug libstdc++/21405] Can't give symbol versions to templates jason at gcc dot gnu dot org
2005-05-05 21:49 [Bug c++/21405] New: Template inlines have global visibility mike at navi dot cx
2005-05-25 23:24 ` [Bug libstdc++/21405] " bkoz at gcc dot gnu dot org
2005-05-31 13:37 ` mike at navi dot cx
2005-05-31 15:29 ` giovannibajo at libero dot it
2005-06-01 11:56 ` mike at navi dot cx
2005-06-03 22:02 ` adam at gimp dot org
2005-08-02 14:28 ` matze at braunis dot de
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=20060320170738.7539.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).