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] xtensa: Revise 89afb2e86fcb29c559b2957fdcbea0d01740c49b
Date: Tue, 24 Jan 2023 13:25:48 -0800	[thread overview]
Message-ID: <CAMo8BfK5v-s5r6vwhUNBv9uwvc64CH4Mso1dZyDFDKtBBRisTw@mail.gmail.com> (raw)
In-Reply-To: <28f483f8-3ace-2150-3352-886a11a9e514@yahoo.co.jp>

On Thu, Jan 19, 2023 at 7:33 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> In the previously posted patch
> "xtensa: Make complex hard register clobber elimination more robust and accurate",
> the check code for insns that refer to the [DS]Cmode hard register before
> it is overwritten after it is clobbered is incomplete.  Fortunately such
> insns are seldom emitted, so it didn't matter.
>
> This patch fixes that for the sake of completeness.
>
> gcc/ChangeLog:
>
>         * config/xtensa/xtensa.md:
>         Fix exit from loops detecting references before overwriting in the
>         split pattern.
> ---
>  gcc/config/xtensa/xtensa.md | 72 +++++++++++++++++++------------------
>  1 file changed, 37 insertions(+), 35 deletions(-)

Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master with more human readable subject line.

-- 
Thanks.
-- Max

      reply	other threads:[~2023-01-24 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28f483f8-3ace-2150-3352-886a11a9e514.ref@yahoo.co.jp>
2023-01-20  3:33 ` Takayuki 'January June' Suwa
2023-01-24 21:25   ` 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=CAMo8BfK5v-s5r6vwhUNBv9uwvc64CH4Mso1dZyDFDKtBBRisTw@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).