From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 2/5] tcg/sparc: Improve code gen for shifted 32-bit constants
Date: Fri, 4 Feb 2022 17:39:42 +0000 [thread overview]
Message-ID: <CAFEAcA8g0GNNx2X3S6uftwymH_6KZHj1=2-eWu9_KKJMYLXr0A@mail.gmail.com> (raw)
In-Reply-To: <20220204070011.573941-3-richard.henderson@linaro.org>
On Fri, 4 Feb 2022 at 07:27, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> We had code for checking for 13 and 21-bit shifted constants,
> but we can do better and allow 32-bit shifted constants.
> This is still 2 insns shorter than the full 64-bit sequence.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2022-02-04 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:00 [PATCH v4 0/5] tcg/sparc: Unaligned access for user-only Richard Henderson
2022-02-04 7:00 ` [PATCH v4 1/5] tcg/sparc: Add scratch argument to tcg_out_movi_int Richard Henderson
2022-02-04 17:35 ` Peter Maydell
2022-02-04 20:42 ` Richard Henderson
2022-02-04 7:00 ` [PATCH v4 2/5] tcg/sparc: Improve code gen for shifted 32-bit constants Richard Henderson
2022-02-04 7:56 ` Philippe Mathieu-Daudé via
2022-02-04 17:39 ` Peter Maydell [this message]
2022-02-04 7:00 ` [PATCH v4 3/5] tcg/sparc: Use the constant pool for 64-bit constants Richard Henderson
2022-02-04 18:18 ` Peter Maydell
2022-02-04 20:41 ` Richard Henderson
2022-02-04 22:20 ` Peter Maydell
2022-02-04 7:00 ` [PATCH v4 4/5] tcg/sparc: Add tcg_out_jmpl_const for better tail calls Richard Henderson
2022-02-04 18:34 ` Peter Maydell
2022-02-04 20:44 ` Richard Henderson
2022-02-04 7:00 ` [PATCH v4 5/5] tcg/sparc: Support unaligned access for user-only Richard Henderson
2022-02-04 19:07 ` Peter Maydell
2022-02-04 20:55 ` 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='CAFEAcA8g0GNNx2X3S6uftwymH_6KZHj1=2-eWu9_KKJMYLXr0A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).