From: "Spider (D.m.D. Lj.)" <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] glibc & binutils -aware hackers wanted for questions ;)
Date: Tue, 29 Nov 2005 02:29:56 +0100 [thread overview]
Message-ID: <1133227796.4229.2.camel@Darkmere.darkmere> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hello,
I've been looking some at Michael Meeks -Bdirect patches, and the
possible performance boost they could give.
The good parts here is that it seems to be far less intrusive for the
running system than prelink is, on the other hand, it does require a
more intrusive surgery into the core systems.
So, now I'm just asking for comments and/or discussion here.. would it
be worth the time spent on this?
http://sourceware.org/ml/binutils/2005-10/msg00436.html
//Spider
--
begin .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-29 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 1:29 Spider (D.m.D. Lj.) [this message]
2005-11-29 1:56 ` [gentoo-dev] glibc & binutils -aware hackers wanted for questions ;) Bret Towe
2005-11-29 2:10 ` Spider (D.m.D. Lj.)
2005-11-29 2:24 ` Bret Towe
2005-12-01 3:03 ` Spider (D.m.D. Lj.)
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=1133227796.4229.2.camel@Darkmere.darkmere \
--to=spider@gentoo.org \
--cc=gentoo-dev@lists.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