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 v4] xtensa: Eliminate the use of callee-saved register that saves and restores only once
Date: Sun, 22 Jan 2023 07:45:03 -0800 [thread overview]
Message-ID: <CAMo8Bf+cws7BD3_Xg2arRVq98E9COr_Syj2PwzTJ=RpZdDUGiA@mail.gmail.com> (raw)
In-Reply-To: <d03c75c4-25e8-c505-d957-f62742c5b642@yahoo.co.jp>
On Fri, Jan 20, 2023 at 8:39 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
> On 2023/01/21 0:14, Max Filippov wrote:
> > After having this many attempts and getting to the issues that are
> > really hard to detect I wonder if the target backend is the right place
> > for this optimization?
> >
> I guess they are not hard to detect
I mean, on the testing side. check-gcc testsuite passed without new
regressions with this change, linux kernel smoke test passed, I was
almost convinced that it's ok to commit.
> but just issues I didn't anticipate (and I just need a little more work).
Looking at other peephole2 patterns I see that their code transformations
are much more compact and they don't need to track additional properties
of unrelated instructions.
> And where else should it be done? What about implementing a
> target-specific pass just for one-point optimization?
I don't even understand what's target-specific in this optimization?
It looks very generic to me.
--
Thanks.
-- Max
next prev parent reply other threads:[~2023-01-22 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <465b0cbe-73ca-f5a0-661d-d34217e29b4d.ref@yahoo.co.jp>
2023-01-19 3:50 ` Takayuki 'January June' Suwa
2023-01-20 15:14 ` Max Filippov
2023-01-21 4:39 ` Takayuki 'January June' Suwa
2023-01-22 15:45 ` Max Filippov [this message]
2023-01-23 3:33 ` Takayuki 'January June' Suwa
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+cws7BD3_Xg2arRVq98E9COr_Syj2PwzTJ=RpZdDUGiA@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).