public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mike at navi dot cx" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/21405] Template inlines have global visibility Date: Sun, 08 May 2005 12:38:00 -0000 [thread overview] Message-ID: <20050508123839.2510.qmail@sourceware.org> (raw) In-Reply-To: <20050505214934.21405.mike@navi.cx> ------- Additional Comments From mike at navi dot cx 2005-05-08 12:38 ------- http://gcc.gnu.org/onlinedocs/libstdc++/abi.html See the "testing multi-abi binaries" section at the bottom: <quote> A "C" application, dynamically linked to two shared libraries, liba, libb. The dependent library liba is C++ shared library compiled with gcc-3.3.x, and uses io, exceptions, locale, etc. The dependent library libb is a C++ shared library compiled with gcc-3.4.x, and also uses io, exceptions, locale, etc. [ ... snip ... ] This resulting binary, when executed, will be able to safely use code from both liba, and the dependent libstdc++.so.6, and libb, with the dependent libstdc++.so.5. </quote> A C++ program linked indirectly (via a C library) against another C++ library is exactly the same scenario. This is the whole point of symbol versioning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21405
next prev parent reply other threads:[~2005-05-08 12:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-05 21:49 [Bug c++/21405] New: " mike at navi dot cx 2005-05-05 22:27 ` [Bug c++/21405] " pinskia at gcc dot gnu dot org 2005-05-05 22:40 ` mike at navi dot cx 2005-05-05 22:40 ` pinskia at gcc dot gnu dot org 2005-05-06 0:17 ` mike at navi dot cx 2005-05-08 12:18 ` chris at bubblescope dot net 2005-05-08 12:38 ` mike at navi dot cx [this message] 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=20050508123839.2510.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: linkBe 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).