From: Nix <nix@esperi.org.uk>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: michael.meeks@novell.com, gcc@gcc.gnu.org
Subject: Re: Large, modular C++ application performance ...
Date: Sat, 30 Jul 2005 13:26:00 -0000 [thread overview]
Message-ID: <87ek9gfmro.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <871x5hs6w0.fsf@deneb.enyo.de> (Florian Weimer's message of "29 Jul 2005 21:19:13 +0100")
On 29 Jul 2005, Florian Weimer announced authoritatively:
> * michael meeks:
>
>> I've been doing a little thinking about how to improve OO.o startup
>> performance recently; and - well, relocation processing happens to be
>> the single, biggest thing that most tools flag.
>
> Have you tried prelinking?
Prelinking is mentioned near the start of the paper and was actually
implemented with OOo (and KDE) in mind.
Alas, it's ineffective for dlopen()ed objects, and OOo dlopen()s nearly
everything. (To my mind the solution is `don't do that then; DT_NEEDED
has a purpose dammit'... certainly this is less disruptive than a change
to the C++ ABI, requiring cooperation with other vendors and a rebuild
of the entire known C++ universe yet again! But I am but an egg in these
waters.)
--
`Tor employs several thousand editors who they keep in dank
subterranean editing facilities not unlike Moria' -- James Nicoll
next prev parent reply other threads:[~2005-07-30 13:26 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 [this message]
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
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=87ek9gfmro.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=michael.meeks@novell.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).