public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bryner at brianryner dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/9283] __attribute__((visibility ("hidden"))) not supported for class/struct
Date: Sun, 18 Apr 2004 03:25:00 -0000 [thread overview]
Message-ID: <20040418022534.27353.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030112104600.9283.mueller@kde.org>
------- 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=<file>
Space separated symbols listed in the <file> 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
next prev parent reply other threads:[~2004-04-18 2:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030112104600.9283.mueller@kde.org>
2003-05-26 22:21 ` pinskia@physics.uc.edu
2003-05-26 22:55 ` mueller@kde.org
2003-05-26 23:05 ` mueller@kde.org
2004-01-29 3:25 ` pinskia at gcc dot gnu dot org
2004-01-30 2:52 ` giovannibajo at libero dot it
2004-01-30 20:51 ` s_gccbugzilla at nedprod dot com
2004-02-01 15:52 ` mueller at kde dot org
2004-02-01 17:29 ` s_gccbugzilla at nedprod dot com
2004-02-20 16:22 ` giovannibajo at libero dot it
2004-02-20 19:33 ` s_gccbugzilla at nedprod dot com
2004-04-04 17:40 ` s_gccbugzilla at nedprod dot com
2004-04-06 22:34 ` s_gccbugzilla at nedprod dot com
2004-04-07 7:03 ` markus+gcc at gyger dot org
2004-04-07 22:17 ` s_gccbugzilla at nedprod dot com
2004-04-18 3:25 ` bryner at brianryner dot com [this message]
2004-04-18 4:19 ` s_gccbugzilla at nedprod dot com
2004-04-18 9:32 ` bryner at brianryner dot com
2004-05-18 10:15 ` s_gccbugzilla at nedprod dot com
2004-07-25 22:52 ` cvs-commit at gcc dot gnu dot org
2004-07-25 23:37 ` pinskia at gcc dot gnu dot org
2004-08-17 3:06 ` cvs-commit at gcc dot gnu dot org
2004-09-01 16:21 ` cvs-commit at gcc dot gnu dot org
[not found] <bug-9283-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:13 ` jackie.rosen at hushmail dot com
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=20040418022534.27353.qmail@sources.redhat.com \
--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: link
Be 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).