From: "H. J. Lu" <hjl@lucon.org>
To: michael meeks <michael.meeks@novell.com>
Cc: Giovanni Bajo <rasky@develer.com>, gcc@gcc.gnu.org
Subject: Re: Large, modular C++ application performance ...
Date: Mon, 01 Aug 2005 15:55:00 -0000 [thread overview]
Message-ID: <20050801155517.GA5095@lucon.org> (raw)
In-Reply-To: <1122889126.19623.105.camel@linux.site>
On Mon, Aug 01, 2005 at 10:38:46AM +0100, michael meeks wrote:
> Hi Giovanni,
>
> On Sat, 2005-07-30 at 15:36 +0200, Giovanni Bajo wrote:
> > I'm slow, but I can't understand why a careful design of the interfaces of
> > the dynamic libraries
>
> Well - sure, depends how 'careful' you are ;-) clearly if no C++
> classes with virtual methods form the interface of any library, then
> there is no problem ;-) unfortunately, mandating that would rather
> cripple C++.
>
> > together with the new -fvisibility flags, should not
> > be sufficient. It worked well in other scenarios
>
> -fvisibility is helpful - as the paper says, not as helpful as the old
> -Bsymbolic (or link maps exposing only 3 or so functions) were. However
> - -fvisibility can only help so much - if you have:
>
Since you were comparing Windows vs. ELF, doesn't Windows need a file
to define which symbols to export for a shared library? Why can't you
you do it with ELF using a linker map? Libstdc++.so is built with
a linker map. Any C++ shared library should use one if the startup
time is a big concern. Of coursee, if gcc can generate a list of
symbols suitable for linker map, which needs to be exported, it will
be very helpful. I don't think it will be too hard to implement.
H.J.
next prev parent reply other threads:[~2005-08-01 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:49 michael meeks
2005-07-29 20:19 ` Florian Weimer
2005-07-30 13:26 ` Nix
2005-07-30 13:36 ` Giovanni Bajo
2005-07-30 17:24 ` Andrew Haley
2005-08-01 9:45 ` michael meeks
2005-08-01 12:18 ` Steven Bosscher
2005-08-02 9:22 ` michael meeks
2005-08-01 9:39 ` michael meeks
2005-08-01 15:55 ` H. J. Lu [this message]
2005-08-02 9:59 ` michael meeks
2005-08-02 13:57 ` H. J. Lu
2005-08-02 16:15 ` michael meeks
2005-08-03 3:07 ` PATCH: Add export to linker map (Re: Large, modular C++ application performance ...) H. J. Lu
2005-08-01 16:59 ` Large, modular C++ application performance Dan Nicolaescu
2005-07-30 15:19 dank
2005-08-01 9:53 ` michael meeks
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=20050801155517.GA5095@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=michael.meeks@novell.com \
--cc=rasky@develer.com \
/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).