From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Will Newton <will.newton@linaro.org>
Cc: Bernie Ogden <bernie.ogden@linaro.org>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Remove arm lowlevellock.c
Date: Tue, 29 Apr 2014 15:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1404291523380.6770@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CANu=Dmjz96Nk-C0xWOdO-xDWzt=+Z7u6OrsYJehcB_Y0T7B=ag@mail.gmail.com>
On Mon, 28 Apr 2014, Will Newton wrote:
> Hi Bernie,
>
> ARM patches can now be sent to libc-alpha as ARM has moved from ports
> into the main tree.
>
> I'm not sure if we still use libc-ports for HPPA patches...
>
> On 28 April 2014 15:50, Bernie Ogden <bernie.ogden@linaro.org> wrote:
> > lowlevellock.c for arm differs from the generic lowlevellock.c only in
> > insignificant ways, so can be removed. Happily, this fixes BZ 15119
> > (unnecessary busy loop in __lll_timedlock_wait on arm).
...
> > Also note that the analysis at
> > https://sourceware.org/ml/libc-ports/2013-02/msg00021.html indicates a
> > further locking performance bug to fix - I've got a partial patch for
> > that which I can submit once I've finished testing.
That analysis asserts that ARM's lowlevellock.c is trying to work around
a bug in lowlevellock.h. Are you asserting in this patch that in fact the
workaround is not needed - that there is no regression caused by removing
the lowlevellock.c file before fixing the lowlevellock.h bug?
(Actually I'd like to see unification of the lowlevellock.h files as far
as possible, not just lowlevellock.c.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-04-29 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:50 Bernie Ogden
2014-04-28 14:56 ` Will Newton
2014-04-29 15:26 ` Joseph S. Myers [this message]
2014-04-30 12:58 ` Bernie Ogden
2014-04-30 15:50 ` Joseph S. Myers
2014-05-01 13:03 ` Bernie Ogden
2014-05-01 13:29 ` Will Newton
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=Pine.LNX.4.64.1404291523380.6770@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bernie.ogden@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=will.newton@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).