From: Dan Nicolaescu <dann@ics.uci.edu>
To: michael.meeks@novell.com
Cc: gcc@gcc.gnu.org
Subject: Re: Large, modular C++ application performance ...
Date: Mon, 01 Aug 2005 16:59:00 -0000 [thread overview]
Message-ID: <200508011657.j71GvmKE025363@scanner2.ics.uci.edu> (raw)
In-Reply-To: <1122666555.19624.25.camel@linux.site>
michael meeks <michael.meeks@novell.com> writes:
> Hi there,
>
> 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 eliminating all the unneeded shared libraries linked to
all the OO.o binaries and shared libraries? This should have an impact on
startup time.
ldd -u -r BINARY_OR_SHARED_LIBRARY
should not print anything
(as a side note Gnome is a much bigger offender on linking way too
many unused shared libraries...)
next prev parent reply other threads:[~2005-08-01 16:59 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
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 ` Dan Nicolaescu [this message]
2005-07-30 15:19 Large, modular C++ application performance 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=200508011657.j71GvmKE025363@scanner2.ics.uci.edu \
--to=dann@ics.uci.edu \
--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).