From: Alexandre Oliva <aoliva@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
arjanv@redhat.com, davej@redhat.com, Ingo Molnar <mingo@elte.hu>
Subject: Re: raid 5 with >= 5 members broken on x86
Date: 26 Feb 2004 19:57:31 -0300 [thread overview]
Message-ID: <or4qtdfnz8.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.LNX.4.58.0402261426460.7830@ppc970.osdl.org>
On Feb 26, 2004, Linus Torvalds <torvalds@osdl.org> wrote:
> Ok. I did the silly one-liner, but if the "don't care" approach really
> improves code generation, feel free to send one that fixes both the P5 and
> PII cases..
FWIW, I think the silly one-liner is actually an improvement, since
then we use a hardware register for the counter, instead of a stack
location. I was concerned about not increasing the register pressure
with the patch; it looked very tight already, and I couldn't tell it
wouldn't be exceeded with some older compiler that failed to eliminate
the frame pointer, for example.
If that's the way to go, I'll post a patch that leaves the +r alone.
If using a stack location for the counter could possibly be as
efficient as using a register, I'd convert "+r" (lines) to "+g". Any
preferences?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Happy GNU Year! oliva@{lsd.ic.unicamp.br, gnu.org}
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2004-02-26 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 18:36 Alexandre Oliva
2004-02-26 21:50 ` Linus Torvalds
2004-02-26 22:04 ` Linus Torvalds
2004-02-26 22:13 ` Alexandre Oliva
2004-02-26 22:32 ` Linus Torvalds
2004-02-26 22:40 ` Alexandre Oliva
2004-02-26 22:57 ` Alexandre Oliva [this message]
2004-02-26 23:37 ` Alexandre Oliva
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=or4qtdfnz8.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®