From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@muc.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Introduce load_TLS to the "for" loop.
Date: Tue, 13 Mar 2007 10:31:27 -0700 [thread overview]
Message-ID: <45F6DFEF.2090008@goop.org> (raw)
In-Reply-To: <20070313135000.GA92373@muc.de>
Andi Kleen wrote:
> On Tue, Mar 13, 2007 at 05:39:36PM +1100, Rusty Russell wrote:
>
>> GCC (4.1 at least) unrolls it anyway, but I can't believe this code
>>
>
> Are you sure? Normally it doesn't unroll without -funroll-loops which
> the kernel does normally not set. Especially not with -Os builds.
>
Does it matter either way in this case?
J
next prev parent reply other threads:[~2007-03-13 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 6:39 [PATCH] Introduce load_TLS to the "for" loop Rusty Russell
2007-03-13 13:50 ` Andi Kleen
2007-03-13 17:31 ` Jeremy Fitzhardinge [this message]
2007-03-13 20:55 ` Andi Kleen
2007-03-14 6:43 ` Rusty Russell
2007-03-14 6:31 ` Rusty Russell
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=45F6DFEF.2090008@goop.org \
--to=jeremy@goop.org \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 NNTP newsgroup(s).