From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] xtensa: Tune "*btrue" insn pattern
Date: Thu, 12 Jan 2023 04:46:17 -0800 [thread overview]
Message-ID: <CAMo8BfKZ7_emhUhGc_WrpvFVhSOu4P17Z46=apAdoKHyckgdPA@mail.gmail.com> (raw)
In-Reply-To: <92692f27-76e3-ce45-bc25-95b9a7d2b64f@yahoo.co.jp>
On Wed, Jan 11, 2023 at 8:26 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> This branch instruction has short encoding if EQ/NE comparison against
> immediate zero when the Code Density Option is enabled, but its "length"
> attribute was only for normal encoding. This patch fixes it.
>
> This patch also prevents undesireable replacement the comparison immediate
> zero of the instruction (short encoding, as mentioned above) with a
> register that has value of zero (normal encoding) by the postreload pass.
>
> gcc/ChangeLog:
>
> * config/xtensa/xtensa.md (*btrue):
> Correct value of the attribute "length" that depends on
> TARGET_DENSITY and operands, and add '?' character to the register
> constraint of the compared operand.
> ---
> gcc/config/xtensa/xtensa.md | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master.
--
Thanks.
-- Max
prev parent reply other threads:[~2023-01-12 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <92692f27-76e3-ce45-bc25-95b9a7d2b64f.ref@yahoo.co.jp>
2023-01-12 4:25 ` Takayuki 'January June' Suwa
2023-01-12 12:46 ` Max Filippov [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='CAMo8BfKZ7_emhUhGc_WrpvFVhSOu4P17Z46=apAdoKHyckgdPA@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jjsuwa_sys3175@yahoo.co.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).