From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] tcg/optimize: only read val after const check
Date: Mon, 28 Feb 2022 10:44:36 -1000 [thread overview]
Message-ID: <9b40e3ff-a7d9-b738-336e-ac552dd40243@linaro.org> (raw)
In-Reply-To: <20220209112142.3367525-1-alex.bennee@linaro.org>
On 2/9/22 01:21, Alex Bennée wrote:
> valgrind pointed out that arg_info()->val can be undefined which will
> be the case if the arguments are not constant. The ordering of the
> checks will have ensured we never relied on an undefined value but for
> the sake of completeness re-order the code to be clear.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tcg/optimize.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks for this. Just missed today's pull, but applied, finally.
r~
>
> diff --git a/tcg/optimize.c b/tcg/optimize.c
> index e573000951..06213fd434 100644
> --- a/tcg/optimize.c
> +++ b/tcg/optimize.c
> @@ -552,10 +552,10 @@ static bool do_constant_folding_cond_eq(TCGCond c)
> static int do_constant_folding_cond(TCGType type, TCGArg x,
> TCGArg y, TCGCond c)
> {
> - uint64_t xv = arg_info(x)->val;
> - uint64_t yv = arg_info(y)->val;
> -
> if (arg_is_const(x) && arg_is_const(y)) {
> + uint64_t xv = arg_info(x)->val;
> + uint64_t yv = arg_info(y)->val;
> +
> switch (type) {
> case TCG_TYPE_I32:
> return do_constant_folding_cond_32(xv, yv, c);
> @@ -567,7 +567,7 @@ static int do_constant_folding_cond(TCGType type, TCGArg x,
> }
> } else if (args_are_copies(x, y)) {
> return do_constant_folding_cond_eq(c);
> - } else if (arg_is_const(y) && yv == 0) {
> + } else if (arg_is_const(y) && arg_info(y)->val == 0) {
> switch (c) {
> case TCG_COND_LTU:
> return 0;
prev parent reply other threads:[~2022-02-28 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:21 [RFC PATCH] tcg/optimize: only read val after const check Alex Bennée
2022-02-09 11:55 ` Philippe Mathieu-Daudé via
2022-02-28 20:44 ` Richard Henderson [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=9b40e3ff-a7d9-b738-336e-ac552dd40243@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.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).