From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14985 invoked by alias); 29 Aug 2005 21:27:21 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 14909 invoked by uid 48); 29 Aug 2005 21:27:17 -0000 Date: Mon, 29 Aug 2005 21:32:00 -0000 Message-ID: <20050829212717.14907.qmail@sourceware.org> From: "mmarcus at emarcus dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050829194742.23628.mmarcus@emarcus.org> References: <20050829194742.23628.mmarcus@emarcus.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/23628] Typeinfo comparison code easily breaks shared libs X-Bugzilla-Reason: CC X-SW-Source: 2005-08/txt/msg03384.txt.bz2 List-Id: ------- Additional Comments From mmarcus at emarcus dot org 2005-08-29 21:27 ------- Suppose for a moment that the boost authors can be convinced to add a bunch of GCC-specific pragmas to their code. Would the problem then be solved? What if a client is using a third party library (maybe a largeley template, header- based library such as boost) in a situation involving shared libraries and non- default visibility. Should the client be expected to figure out exactly which pieces of the library make use of RTTI (as an implementation detail) so that they can set visibility of client-defined types to default, in order to avoid possibly silent failure of the library when it uses RTTI upon those types? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23628