From: Yannick Koehler <yannick.koehler@colubris.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Fwd: Objprelink revisited.
Date: Mon, 17 Jun 2002 16:36:51 -0400 [thread overview]
Message-ID: <200206171636.54490.yannick.koehler@colubris.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I thought this may be of interests.
- ---------- Forwarded Message ----------
Subject: Objprelink revisited.
Date: Mon, 17 Jun 2002 16:14:54 -0400
From: Leon Bottou <leon@bottou.org>
To: kde-devel@kde.org
John Ryland and I did some extra-work on objprelink.
Overview, explanations, details and benchmarks can be found in:
http://objprelink.sourceforge.net/objprelink.html
Summary of the conclusions:
- - Recent binutils have been improved and now offer
performance similar to the old version of objprelink.
In fact, the new binutils and the old objprelink
are two different ways to achieve the same
complexity reduction.
- - A new version, objprelink2, gives a new runtime link speedup.
But it no longer translate into improved KDE responsiveness
because the runtime linker delay is now a small component
of the application startup time.
I do not suggest using objprelink2 unless
your linux box lacks the improved binutils.
See <http://objprelink.sourceforge.net/> to check.
Be warned that objprelink is not a production tool.
This is more a research tool whose ideas, hopefully,
might be useful to others.
I also suggest removing the --enable-objprelink from
the KDE configure. Those who need objprelink will
use objprelink2 and will not need this option.
- - Leon Bottou
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
>> <<
- -------------------------------------------------------
- --
Yannick Koehler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9DkhkfuKOJNEyL1URAke7AKCY8B3k6ifsO7nCXZK6ni/f4ih/LQCfUnGm
mH4FQLrh0zqh344uaXWOToo=
=jnkU
-----END PGP SIGNATURE-----
reply other threads:[~2002-06-17 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200206171636.54490.yannick.koehler@colubris.com \
--to=yannick.koehler@colubris.com \
--cc=gentoo-dev@gentoo.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