From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27383 invoked by alias); 18 Apr 2004 02:25:34 -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 27354 invoked by uid 48); 18 Apr 2004 02:25:34 -0000 Date: Sun, 18 Apr 2004 03:25:00 -0000 Message-ID: <20040418022534.27353.qmail@sources.redhat.com> From: "bryner at brianryner dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20030112104600.9283.mueller@kde.org> References: <20030112104600.9283.mueller@kde.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/9283] __attribute__((visibility ("hidden"))) not supported for class/struct X-Bugzilla-Reason: CC X-SW-Source: 2004-04/txt/msg01469.txt.bz2 List-Id: ------- Additional Comments From bryner at brianryner dot com 2004-04-18 02:25 ------- I posted a new patch here based on earlier review comments: http://gcc.gnu.org/ml/gcc-patches/2004-04/msg00240.html I like the idea of moving forward on -fvisibility as well, but we need a way to address the fact that current DSO header files on unix don't normally specify default visibility. Intel's compiler has additional options, such as: -fvisibility-default= Space separated symbols listed in the argument will get visibility set to default This type of file could be generated by running nm over the shared libraries you plan to link against. Unfortunately I haven't been able to figure out how to get the symbol name for a decl (exactly as it would be output in the assembly), to compare against a list of symbols generated with nm. Niall, I assume you just changed the relevant system headers to specify default visibility? I think we'd be causing a lot of headaches if we tried to force all library maintainers to do this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9283