public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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 2/5] xtensa: Make use of IN_RANGE macro where appropriate
Date: Thu, 26 May 2022 09:42:59 -0700	[thread overview]
Message-ID: <CAMo8Bf+g_ujw1WpExc4-vP3-H44NMz=XBPPRdNMJ6_rmN1fM8g@mail.gmail.com> (raw)
In-Reply-To: <910788ae-597e-5564-88ea-cbda6de285a0@yahoo.co.jp>

On Fri, May 13, 2022 at 6:35 AM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> No functional changes.
>
> gcc/ChangeLog:
>
>         * gcc/config/xtensa/constraints.md (M, O): Use the macro.
>         * gcc/config/xtensa/predicates.md (addsubx_operand, extui_fldsz_operand,
>         sext_fldsz_operand): Ditto.
>         * gcc/config/xtensa/xtensa.cc (xtensa_simm8, xtensa_simm8x256,
>         xtensa_simm12b, xtensa_uimm8, xtensa_uimm8x2, xtensa_uimm8x4,
>         xtensa_mask_immediate, smalloffset_mem_p, printx, xtensa_call_save_reg,
>         xtensa_expand_prologue): Ditto.
>         * gcc/config/xtensa/xtensa.h (FUNCTION_ARG_REGNO_P): Ditto.
> ---
>   gcc/config/xtensa/constraints.md |  4 ++--
>   gcc/config/xtensa/predicates.md  |  5 ++---
>   gcc/config/xtensa/xtensa.cc      | 20 ++++++++++----------
>   gcc/config/xtensa/xtensa.h       |  2 +-
>   4 files changed, 15 insertions(+), 16 deletions(-)

Regtested for target=xtensa-linux-uclibc, no new regressions.
Changelog has extra 'gcc/' in paths, so I've dropped this part.
Committed to master.

-- 
Thanks.
-- Max

      reply	other threads:[~2022-05-26 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 13:27 Takayuki 'January June' Suwa
2022-05-26 16:42 ` 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='CAMo8Bf+g_ujw1WpExc4-vP3-H44NMz=XBPPRdNMJ6_rmN1fM8g@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).