public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "s_gccbugzilla at nedprod 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, 04 Apr 2004 17:40:00 -0000 [thread overview]
Message-ID: <20040404174008.26392.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030112104600.9283.mueller@kde.org>
------- Additional Comments From s_gccbugzilla at nedprod dot com 2004-04-04 17:40 -------
(In reply to comment #11)
> This makes it easier to add the -fvisibility=X command line switches to GCC
> later on.
This is to let you all know that I have taken Brian Ryner's patch and used it to
implement a further patch against GCC v3.4 CVS adding the -fvisibility
functionality I previously described with appropriate documentation patching
too. I am currently testing my patch though I should be finished by tonight.
Using my new patch, I have reduced the dynamic symbol table of my library,
TnFOX, from 16342 symbols down to 9590 with no special measures and no problems.
Furthermore the binary size has dropped as my patch marks many more symbols as
local and thus their access code can be optimised.
I am just about to embark on compiling the Boost.Python based python bindings
for TnFOX. They previously had >250,000 symbols and took six minutes for
anything linked against them to load - even after applying a filtering version
script, I could only get it down to ~76,000 which at least linked in less than
ten seconds. With my new GCC, I am expecting to reduce this to less than 1000
symbols with a substantial reduction of binary size (it's currently 130Mb) as
lots of RTTI can be elided.
I'll get back to you when I have built the bindings (it takes nine hours).
Cheers,
Niall
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9283
next prev parent reply other threads:[~2004-04-04 17:40 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 [this message]
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
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=20040404174008.26392.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).