From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Cc: Michael Tokarev <mjt@tls.msk.ru>, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for 1.5] tcg/optimize: fix setcond2 optimization
Date: Wed, 8 May 2013 22:49:31 +0200 [thread overview]
Message-ID: <20130508204931.GF31148@hall.aurel32.net> (raw)
In-Reply-To: <1368045762-9769-1-git-send-email-aurelien@aurel32.net>
On Wed, May 08, 2013 at 10:42:42PM +0200, Aurelien Jarno wrote:
> When setcond2 is rewritten into setcond, the state of the destination
> temp should be reset, so that a copy of the previous value is not
> used instead of the result.
>
> Reported-by: Michael Tokarev <mjt@tls.msk.ru>
> Cc: Richard Henderson <rth@twiddle.net>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> ---
> tcg/optimize.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tcg/optimize.c b/tcg/optimize.c
> index 1b6644c..b35868a 100644
> --- a/tcg/optimize.c
> +++ b/tcg/optimize.c
> @@ -1057,6 +1057,7 @@ static TCGArg *tcg_constant_folding(TCGContext *s, uint16_t *tcg_opc_ptr,
> /* Simplify LT/GE comparisons vs zero to a single compare
> vs the high word of the input. */
> s->gen_opc_buf[op_index] = INDEX_op_setcond_i32;
> + reset_temp(args[0]);
> gen_args[0] = args[0];
> gen_args[1] = args[2];
> gen_args[2] = args[4];
I have just noticed that the problem is there since release 1.3, even if
it appeared more clearly only with commit 7eb0cc85. All 64-bit targets
on 32-bit hosts are possibly affected.
Therefore it should be fixed in the next stable releases. Hence the Cc
to qemu-stable@nongnu.org.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2013-05-08 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 20:42 [Qemu-devel] [PATCH for 1.5] tcg/optimize: fix setcond2 optimization Aurelien Jarno
2013-05-08 20:49 ` Aurelien Jarno [this message]
2013-05-09 13:03 ` 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=20130508204931.GF31148@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.