public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Vladimir Makarov <vmakarov.gcc@gmail.com>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [pushed] [RA]: Modify cost calculation for dealing with pseudo equivalences
Date: Fri, 27 Oct 2023 16:25:54 +0200	[thread overview]
Message-ID: <CAPS5kha=RnXO3epUq+O6yweqp6Ab7+JBS8GWHbOeH5p1jG99gA@mail.gmail.com> (raw)
In-Reply-To: <41540801-74ec-b9bd-3a33-96a8ed4deaed@redhat.com>

On Fri, 27 Oct 2023 at 16:19, Vladimir Makarov <vmakarov@redhat.com> wrote:
>
>
> On 10/27/23 09:56, Christophe Lyon wrote:
> > Hi Vladimir,
> >
> > On Thu, 26 Oct 2023 at 16:00, Vladimir Makarov <vmakarov.gcc@gmail.com> wrote:
> >> This is the second attempt to improve RA cost calculation for pseudos
> >> with equivalences.  The patch explanation is in the log message.
> >>
> >> The patch was successfully bootstrapped and tested on x86-64, aarch64,
> >> and ppc64le.  The patch was also benchmarked on x86-64 spec2017.
> >> specfp2017 performance did not changed, specint2017 improved by 0.3%.
> >>
> > As reported by our CI, this patch causes a regression on arm:
> > FAIL: gcc.target/arm/eliminate.c scan-assembler-times r0,[\\t ]*sp 3
> >
> >
> > For this testcase, we used to generate:
> >          str     lr, [sp, #-4]!
> >          sub     sp, sp, #12
> >          add     r0, sp, #4
> >          bl      bar
> >          add     r0, sp, #4
> >          bl      bar
> >          add     r0, sp, #4
> >          bl      bar
> >          add     sp, sp, #12
> >          ldr     lr, [sp], #4
> >          bx      lr
> >
> > After your patch, we generate:
> >          push    {r4, lr}
> >          sub     sp, sp, #8
> >          add     r4, sp, #4
> >          mov     r0, r4
> >          bl      bar
> >          mov     r0, r4
> >          bl      bar
> >          mov     r0, r4
> >          bl      bar
> >          add     sp, sp, #8
> >          pop     {r4, lr}
> >          bx      lr
> >
> > which uses 1 more register and 1 more instruction.
> >
> > Shall I file a bugzilla report for this?
> >
> I started to work on this right after I got the message (yesterday).  I
> already have a patch and am going to commit it during an hour.  So there
> is no need to fill the PR.
>
Great, thanks for the quick fix!

  reply	other threads:[~2023-10-27 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 14:00 Vladimir Makarov
2023-10-27 13:56 ` Christophe Lyon
2023-10-27 14:18   ` Vladimir Makarov
2023-10-27 14:25     ` Christophe Lyon [this message]
2023-11-07 16:18 ` Saurabh Jha

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='CAPS5kha=RnXO3epUq+O6yweqp6Ab7+JBS8GWHbOeH5p1jG99gA@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vmakarov.gcc@gmail.com \
    --cc=vmakarov@redhat.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).