public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmarcus at emarcus dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/23628] Typeinfo comparison code easily breaks shared libs Date: Mon, 29 Aug 2005 22:14:00 -0000 [thread overview] Message-ID: <20050829215732.7347.qmail@sourceware.org> (raw) In-Reply-To: <20050829194742.23628.mmarcus@emarcus.org> ------- Additional Comments From mmarcus at emarcus dot org 2005-08-29 21:57 ------- Maybe I should rephrase my concern as the following question. Suppose a gcc user is building an application and some shared libraries that depend on third party libraries. Under what circumstances can he safely set visibility to someting other than default, for any types? My current understanding is that it is only safe to do so for types whose typeinfo will he can guarantee will never be shared. This is not always an easy guarantee to make, and so, if my undersatanding is correct, makes hidden visibility much less useful than it first appears. If typeinfo equality was based on string comparison instead of address comparison, the usefuleness of hidden visibility would be greatly increased. This would also address another important use case. There is often a desire to produce a shared library with only an extern "C" ABI, especially when building artifacts designed for long-term binary compatibility. That is, the only visible symbols should be extern "C" functions. To write such a shared library in C++, while depending upon a shared libstdc++ or other shared C++ libraries is not possible if one most make typeinfo visible just to share it with the libraries upon which our library depends. Address-only typeinfo equality comparison has a high usability cost. Would it be possible to first check for address equality, falling back to a string comparison upon failure? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23628
next prev parent reply other threads:[~2005-08-29 21:57 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-29 19:55 [Bug c++/23628] New: " mmarcus at emarcus dot org 2005-08-29 19:58 ` [Bug c++/23628] " pinskia at gcc dot gnu dot org 2005-08-29 19:59 ` pinskia at gcc dot gnu dot org 2005-08-29 20:23 ` mmarcus at emarcus dot org 2005-08-29 20:27 ` mmarcus at emarcus dot org 2005-08-29 20:30 ` pinskia at gcc dot gnu dot org 2005-08-29 20:31 ` pinskia at gcc dot gnu dot org 2005-08-29 20:34 ` pinskia at gcc dot gnu dot org 2005-08-29 20:40 ` pinskia at gcc dot gnu dot org 2005-08-29 20:49 ` mmarcus at emarcus dot org 2005-08-29 20:56 ` pinskia at gcc dot gnu dot org 2005-08-29 20:57 ` pinskia at gcc dot gnu dot org 2005-08-29 21:01 ` mmarcus at emarcus dot org 2005-08-29 21:05 ` mmarcus at emarcus dot org 2005-08-29 21:11 ` pinskia at gcc dot gnu dot org 2005-08-29 21:32 ` mmarcus at emarcus dot org 2005-08-29 21:32 ` Andrew Pinski 2005-08-29 21:57 ` pinskia at physics dot uc dot edu 2005-08-29 22:14 ` mmarcus at emarcus dot org [this message] 2005-08-30 13:17 ` ghost at cs dot msu dot su 2005-08-30 13:44 ` gdr at integrable-solutions dot net 2005-08-31 7:19 ` ghost at cs dot msu dot su 2005-08-31 14:21 ` pinskia at gcc dot gnu dot org 2005-08-31 14:39 ` ghost at cs dot msu dot su 2005-08-31 14:56 ` gdr at integrable-solutions dot net 2005-09-01 8:35 ` mmarcus at emarcus dot org 2005-09-01 10:42 ` s_gccbugzilla at nedprod dot com [not found] <bug-23628-10681@http.gcc.gnu.org/bugzilla/> 2006-01-21 21:02 ` rjohnson at dogstar-interactive dot com 2006-01-21 21:45 ` gdr at cs dot tamu dot edu 2006-09-18 21:02 ` geoffk at gcc dot gnu dot org
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=20050829215732.7347.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).