From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nick Piggin <npiggin@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nick Piggin <npiggin@kernel.dk>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 0/6] Clean up ticketlock implementation
Date: Mon, 31 Jan 2011 13:46:50 -0800 [thread overview]
Message-ID: <4D472DCA.8080402@goop.org> (raw)
In-Reply-To: <AANLkTikPfjzpQn4nYgoAyAJ6sDnZM-a0b3V794Q_Mpy+@mail.gmail.com>
On 01/24/2011 05:08 PM, Nick Piggin wrote:
>> So very similar, except the compiler misses directly comparing
>> %ah to %al.
> Oh :(
>
> Have you filed a bug with gcc?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47556
J
prev parent reply other threads:[~2011-01-31 21:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:41 [PATCH 0/6] Clean up ticketlock implementation Jeremy Fitzhardinge
2011-01-24 23:41 ` [PATCH 1/6] x86/ticketlock: clean up types and accessors Jeremy Fitzhardinge
2011-01-24 23:41 ` [PATCH 2/6] x86/ticketlock: convert spin loop to C Jeremy Fitzhardinge
2011-01-24 23:41 ` [PATCH 3/6] x86/ticketlock: Use C for __ticket_spin_unlock Jeremy Fitzhardinge
2011-01-25 1:13 ` Nick Piggin
2011-01-25 1:42 ` Jeremy Fitzhardinge
2011-01-25 1:49 ` Nick Piggin
2011-01-24 23:41 ` [PATCH 4/6] x86/ticketlock: make large and small ticket versions of spin_lock the same Jeremy Fitzhardinge
2011-01-24 23:41 ` [PATCH 5/6] x86/ticketlock: make __ticket_spin_lock common Jeremy Fitzhardinge
2011-01-24 23:41 ` [PATCH 6/6] x86/ticketlock: make __ticket_spin_trylock common Jeremy Fitzhardinge
2011-01-25 1:16 ` Nick Piggin
2011-01-25 1:42 ` Jeremy Fitzhardinge
2011-01-25 1:58 ` Nick Piggin
2011-01-27 23:53 ` Jeremy Fitzhardinge
2011-01-25 1:08 ` [PATCH 0/6] Clean up ticketlock implementation Nick Piggin
2011-01-31 21:46 ` Jeremy Fitzhardinge [this message]
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=4D472DCA.8080402@goop.org \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@gmail.com \
--cc=npiggin@kernel.dk \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.