From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: fix dead computation for repeated input arguments
Date: Thu, 21 May 2015 20:35:54 +0200 [thread overview]
Message-ID: <20150521183554.GA8235@aurel32.net> (raw)
In-Reply-To: <555B4CAC.30805@twiddle.net>
On 2015-05-19 07:46, Richard Henderson wrote:
> On 05/19/2015 03:26 AM, Aurelien Jarno wrote:
> > @@ -1522,6 +1522,9 @@ static void tcg_liveness_analysis(TCGContext *s)
> > if (dead_temps[arg]) {
> > dead_args |= (1 << i);
> > }
> > + }
> > + for (i = nb_oargs; i < nb_oargs + nb_iargs; i++) {
> > + arg = args[i];
> > dead_temps[arg] = 0;
> > }
> > s->op_dead_args[oi] = dead_args;
>
> How about another line of commentary for each loop?
>
> Something like
>
> /* Record arguments that die in this opcode. */
>
> for the first and
>
> /* Input arguments are live for preceeding opcodes. */
>
> for the second.
Good point.
> As for the same loop for calls, you're right that it may well cause us to do a
> tiny bit of redundant work, but nothing else bad will happen. We'll enter
> temp_dead more times than necessary. I'm always skeptical about knowingly
> giving a compiler bad information though. You tend to not know how data is
> going to be used in future, and *then* get bad results.
You are correct. Anyway I don't think it'll make a big difference in
performance.
I'll send a new version of the patch.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2015-05-21 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 10:26 [Qemu-devel] [PATCH] tcg: fix dead computation for repeated input arguments Aurelien Jarno
2015-05-19 14:46 ` Richard Henderson
2015-05-21 18:35 ` Aurelien Jarno [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=20150521183554.GA8235@aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.