From: Max Filippov <jcmvbkbc@gmail.com>
To: Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] xtensa: Simplify several MD templates
Date: Fri, 31 May 2024 14:46:01 -0700 [thread overview]
Message-ID: <ZlpFGffPhMs5S5F9@octofox.metropolis> (raw)
In-Reply-To: <414a8bdd-e4c4-4515-a179-50ee7cafd62d@yahoo.co.jp>
On Fri, May 31, 2024 at 07:23:13PM +0900, Takayuki 'January June' Suwa wrote:
> No functional changes.
>
> gcc/ChangeLog:
>
> * config/xtensa/predicates.md
> (subreg_HQI_lowpart_operator, xtensa_sminmax_operator):
> New operator predicates.
> * config/xtensa/xtensa-protos.h (xtensa_match_CLAMPS_imms_p):
> Remove.
> * config/xtensa/xtensa.cc (xtensa_match_CLAMPS_imms_p): Ditto.
> * config/xtensa/xtensa.md
> (*addsubx, *extzvsi-1bit_ashlsi3, *extzvsi-1bit_addsubx):
> Revise the output statements by conditional ternary operator rather
> than switch-case clause in order to avoid using gcc_unreachable().
> (xtensa_clamps): Reduce to a single pattern definition using the
> predicate added above.
> (Some split patterns to assist *masktrue_const_bitcmpl): Ditto.
> ---
> gcc/config/xtensa/predicates.md | 23 +++++++
> gcc/config/xtensa/xtensa-protos.h | 1 -
> gcc/config/xtensa/xtensa.cc | 10 ---
> gcc/config/xtensa/xtensa.md | 109 ++++++------------------------
> 4 files changed, 43 insertions(+), 100 deletions(-)
Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master.
Suwa-san, something has changed in your mail setup apparently: every
patch context line now gets an extra space in the beginning. Could you
please fix that?
--
Thanks.
-- Max
prev parent reply other threads:[~2024-05-31 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <414a8bdd-e4c4-4515-a179-50ee7cafd62d.ref@yahoo.co.jp>
2024-05-31 10:23 ` Takayuki 'January June' Suwa
2024-05-31 21: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=ZlpFGffPhMs5S5F9@octofox.metropolis \
--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).