From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15811 invoked by alias); 31 Aug 2005 14:48:15 -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 15743 invoked by alias); 31 Aug 2005 14:48:07 -0000 Date: Wed, 31 Aug 2005 14:56:00 -0000 Message-ID: <20050831144807.15742.qmail@sourceware.org> From: "gdr at integrable-solutions dot net" 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/msg03593.txt.bz2 List-Id: ------- Additional Comments From gdr at integrable-solutions dot net 2005-08-31 14:48 ------- Subject: Re: Typeinfo comparison code easily breaks shared libs "ghost at cs dot msu dot su" writes: | You might be formally right, but what about practical consequences? Unless | *all* libraries I use have push/pops in *every single header*, using | -fvisibility for my own library can result in crash. So for a large | application you'd need to get authors of all used libraries to "fix" them! | Note that even libstdc++ does not have this at the moment. This makes | -fvisibility just useless. Please, reopen this PR. Andrew, take a deep breadth. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23628