qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	Mike Frysinger <vapier@gentoo.org>,
	Anthony Green <green@moxielogic.com>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org,
	Max Filippov <jcmvbkbc@gmail.com>,
	Michael Walle <michael@walle.cc>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] [PATCH qom-cpu 0/5] TCG code generation performance fix
Date: Tue, 02 Jul 2013 22:13:41 +0200	[thread overview]
Message-ID: <51D33475.2040405@suse.de> (raw)
In-Reply-To: <51D33119.5050209@twiddle.net>

Am 02.07.2013 21:59, schrieb Richard Henderson:
> On 07/02/2013 12:31 PM, Andreas Färber wrote:
>> Hello,
>>
>> As Richard explained, the purpose of having separate gen_intermediate_code()
>> and gen_intermediate_code_pc() functions per target is to compile-optimize
>> gen_intermediate_code_internal() for the non-_pc case.
>>
>> Multiple targets were using static rather than static inline though, fix this.
>>
>> I've split these off from my refactorings so that we can backport them to stable,
>> and I'm rebasing my argument refactoring patches on top.
>>
>> No actual performance changes have been benchmarked, these changes serve more
>> to align our targets as clear examples for new targets such as rl78 and bfin.
> 
> All:
> Reviewed-by: Richard Henderson <rth@twiddle.net>
> 
> Although we should probably do some benchmarking at some point to see if
> the duplicated code paths really do improve things over, say, unlikely().

I did wonder about unlikely() last night, but I thought that's just a
branch optimization whereas inline might avoid some branches in the
first place.

> But failing that we should at least have conformity of implementation.

Thanks, applied to qom-cpu (moving log_cpu_state to qom-cpu-next):
https://github.com/afaerber/qemu-cpu/commits/qom-cpu
(If maintainers want to ack/nack, please do.)

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2013-07-02 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 19:31 [Qemu-devel] [PATCH qom-cpu 0/5] TCG code generation performance fix Andreas Färber
2013-07-02 19:31 ` [Qemu-devel] [PATCH qom-cpu 1/5] target-cris: gen_intermediate_code_internal() should be inlined Andreas Färber
2013-07-02 19:31 ` [Qemu-devel] [PATCH qom-cpu 2/5] target-lm32: gen_intermediate_code_internal() should be inline Andreas Färber
2013-07-02 21:16   ` Michael Walle
2013-07-02 19:31 ` [Qemu-devel] [PATCH qom-cpu 3/5] target-microblaze: " Andreas Färber
2013-07-02 19:31 ` [Qemu-devel] [PATCH qom-cpu 4/5] target-moxie: " Andreas Färber
2013-07-02 19:31 ` [Qemu-devel] [PATCH qom-cpu 5/5] target-xtensa: " Andreas Färber
2013-07-02 19:59 ` [Qemu-devel] [PATCH qom-cpu 0/5] TCG code generation performance fix Richard Henderson
2013-07-02 20:13   ` Andreas Färber [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=51D33475.2040405@suse.de \
    --to=afaerber@suse.de \
    --cc=edgar.iglesias@gmail.com \
    --cc=green@moxielogic.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=michael@walle.cc \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=vapier@gentoo.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 NNTP newsgroup(s).