From: michael meeks <michael.meeks@novell.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Martin Hollmichel - Sun Germany - ham02 - Hamburg
<martin.hollmichel@Sun.COM>, Giovanni Bajo <rasky@develer.com>,
gcc@gcc.gnu.org
Subject: Re: Large, modular C++ application performance ...
Date: Tue, 02 Aug 2005 16:15:00 -0000 [thread overview]
Message-ID: <1122999276.25655.125.camel@linux.site> (raw)
In-Reply-To: <20050802135722.GA23692@lucon.org>
On Tue, 2005-08-02 at 06:57 -0700, H. J. Lu wrote:
> Maitaining a C++ linker map isn't easy. I think gcc should help out
> here.
What do you suggest ? - something separate from the visibility markup ?
perhaps what I'm suggesting is some horribly mis-use of that. Clearly
adding a new visibility attribute that would bind that symbol
internally, yet export it would be a simple approach; did you have a
better idea ? and/or suggestions for a name ? - or is this a total
non-starter for some other reason ?
> > That would suit our needs beautifully - if, when used to annotate a
> > class, it would allow the various typeinfo / vague-linkage pieces
> > through as 'default'. Is it a realistic suggestion ? / if so, am happy
> > to knock up a patch.
> >
> > [ and of course, this is only 1/2 the problem - the other half isn't
> > much helped by visibility markup as previously discussed ;-]
>
> Why not? If you know a symbol in DSO won't be overridden by others,
> you can resolve it locally via a linker map.
Sure - the other (more than) 1/2 of the performance problem comes from
named relocations to symbols external to the DSO.
Thanks,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
next prev parent reply other threads:[~2005-08-02 16:15 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
2005-08-02 9:59 ` michael meeks
2005-08-02 13:57 ` H. J. Lu
2005-08-02 16:15 ` michael meeks [this message]
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=1122999276.25655.125.camel@linux.site \
--to=michael.meeks@novell.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=martin.hollmichel@Sun.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).