From: "Andreas Färber" <afaerber@suse.de>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] ARM: AREG0 conversion
Date: Mon, 26 Mar 2012 14:48:26 +0200 [thread overview]
Message-ID: <4F70659A.3070201@suse.de> (raw)
In-Reply-To: <87sjgvh6nm.fsf@ginnungagap.bsc.es>
Am 26.03.2012 14:46, schrieb Lluís Vilanova:
> Peter Maydell writes:
>
>> On 24 March 2012 18:58, Blue Swirl <blauwirbel@gmail.com> wrote:
>>> v2: fix patch 1, tweak patch 2 and rebase to master.
>>>
>>> URL git://repo.or.cz/qemu/blueswirl.git
>>> http://repo.or.cz/r/qemu/blueswirl.git
>>>
>>> Blue Swirl (6):
>>> arm: move neon_tbl to neon_helper.c
>>> arm: move saturating arithmetic to helper.c
>>> arm: move other arithmetic to helper.c
>>> arm: move cpsr and banked register access to helper.c
>>> arm: move exception and wfi helpers to helper.c
>>> arm: move load and store helpers, switch to AREG0 free mode
>
>> The patches themselves look OK, but do we really want to take
>> a 5% performance hit for this cleanup?
>
> I was also wondering this. Is there any plan for recovering that 5% afterwards?
Maybe by switching to clang? ;)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-26 12:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 18:58 [Qemu-devel] [PATCH v2 0/6] ARM: AREG0 conversion Blue Swirl
2012-03-25 22:29 ` Richard Henderson
2012-03-26 11:52 ` Peter Maydell
2012-03-26 12:46 ` Lluís Vilanova
2012-03-26 12:48 ` Andreas Färber [this message]
2012-03-26 13:05 ` Paul Brook
2012-03-26 17:02 ` Blue Swirl
2012-03-26 17:59 ` Lluís Vilanova
2012-03-27 13:40 ` Laurent Desnogues
2012-03-27 16:48 ` Blue Swirl
2012-03-27 17:01 ` Laurent Desnogues
2012-03-27 19:59 ` Artyom Tarasenko
2012-03-29 15:42 ` Laurent Desnogues
2012-03-29 16:28 ` Richard Henderson
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=4F70659A.3070201@suse.de \
--to=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).