public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Spider (D.m.D. Lj.)" <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] glibc & binutils -aware hackers wanted for questions ;)
Date: Tue, 29 Nov 2005 03:10:10 +0100	[thread overview]
Message-ID: <1133230210.4229.5.camel@Darkmere.darkmere> (raw)
In-Reply-To: <dda83e780511281756y137aaa56mc7bede3bf9cc4e07@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

On Mon, 2005-11-28 at 17:56 -0800, Bret Towe wrote:

> >
> > 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
> 
> looks interesting personally id like to see how it acts on kde also
> and some small c++ apps to see if it hurts them any
> a single benchmark for a change that would affect so much seems
> a bit silly to me

Yeah, but before I start to spend too much time hacking on this, I'd
want to have a suggested metric and performance test setup here. If
anyone has ideas for a decent test, I'd be happy.

As for KDE, I think modern Gnome would benefit as well, since it has
been heavily refactioned into libraries these days. 

//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 --]

  reply	other threads:[~2005-11-29  2:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29  1:29 [gentoo-dev] glibc & binutils -aware hackers wanted for questions ;) Spider (D.m.D. Lj.)
2005-11-29  1:56 ` Bret Towe
2005-11-29  2:10   ` Spider (D.m.D. Lj.) [this message]
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=1133230210.4229.5.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