From: Oleg Endo <oleg.endo@t-online.de>
To: Jeff Law <jeffreyalaw@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Remove compromised sh test
Date: Thu, 27 Jun 2024 07:44:20 +0900 [thread overview]
Message-ID: <f0e8dc4de9e28694365d6c87744864119d8a77aa.camel@t-online.de> (raw)
In-Reply-To: <5e3df9ed-dc09-4f86-8bfb-e33d11d6be6f@gmail.com>
On Wed, 2024-06-26 at 16:39 -0600, Jeff Law wrote:
>
> On 6/26/24 4:12 PM, Oleg Endo wrote:
> >
> >
> > On Wed, 2024-06-26 at 07:22 -0600, Jeff Law wrote:
> > > Surya's recent patch to IRA improves the code for sh/pr54602-1.c
> > > slightly. Specifically it's able to eliminate a save/restore in the
> > > prologue/epilogue and a bit of register shuffling.
> > >
> > > As a result there literally aren't any insns that can be used to fill
> > > the delay slot of the return, so a nop gets emitted and the test fails.
> > >
> > > Given there literally aren't any insns to move into the delay slot, the
> > > best course of action is to just drop the test.
> > >
> > > Pushed to the trunk.
> > >
> > > Jeff
> >
> > I can't reproduce what you are saying.
> > Which triplet and flags is your test setup using?
> >
> > For this test case, GCC 13 with -m4 -ml -O1 -fno-pic:
> No -m flags at all. As plain of a testrun as you can do.
>
OK, then what's the default config of your test setup / triplet?
Can you please show the generated code that you get? Because - like I said
- I can't reproduce it.
Best regards,
Oleg Endo
next prev parent reply other threads:[~2024-06-26 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 13:22 Jeff Law
2024-06-26 22:12 ` Oleg Endo
2024-06-26 22:39 ` Jeff Law
2024-06-26 22:44 ` Oleg Endo [this message]
2024-06-27 0:30 ` Jeff Law
2024-06-27 1:27 ` Oleg Endo
2024-06-27 1:54 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 13:21 Jeff Law
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=f0e8dc4de9e28694365d6c87744864119d8a77aa.camel@t-online.de \
--to=oleg.endo@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).