public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
	"jakub@redhat.com" <jakub@redhat.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	Richard Biener <rguenther@suse.de>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: RE: [backport gcc10, gcc9] Requet to backport PR97969
Date: Thu, 3 Jun 2021 08:54:13 +0000	[thread overview]
Message-ID: <PAXPR08MB66210BF964672378A2D3CD32E43C9@PAXPR08MB6621.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAKdteOb29VEEN2iwk-i4Co82-uLLi_ctfC5-E8_p9spuEnB++A@mail.gmail.com>



> -----Original Message-----
> From: Christophe Lyon <christophe.lyon@linaro.org>
> Sent: 03 June 2021 09:45
> To: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
> Cc: Vladimir Makarov <vmakarov@redhat.com>; jakub@redhat.com; Richard
> Earnshaw <Richard.Earnshaw@arm.com>; Richard Biener
> <rguenther@suse.de>; gcc-patches@gcc.gnu.org; Ramana Radhakrishnan
> <Ramana.Radhakrishnan@arm.com>
> Subject: Re: [backport gcc10, gcc9] Requet to backport PR97969
> 
> On Thu, 3 Jun 2021 at 00:31, Przemyslaw Wirkus via Gcc-patches <gcc-
> patches@gcc.gnu.org> wrote:
> >
> > Hi,
> >
> > > -----Original Message-----
> > > From: Vladimir Makarov <vmakarov@redhat.com>
> > > Sent: 31 May 2021 16:52
> > > To: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>; Richard Biener
> > > <rguenther@suse.de>
> > > Cc: gcc-patches@gcc.gnu.org; jakub@redhat.com; nickc@redhat.com;
> > > Richard Earnshaw <Richard.Earnshaw@arm.com>; Ramana
> Radhakrishnan
> > > <Ramana.Radhakrishnan@arm.com>; Kyrylo Tkachov
> > > <Kyrylo.Tkachov@arm.com>
> > > Subject: Re: [backport gcc10, gcc9] Requet to backport PR97969
> > >
> > >
> > > On 2021-05-25 5:14 a.m., Przemyslaw Wirkus wrote:
> > > > Hi,
> > > > Just a follow up after GCC 11 release.
> > > >
> > > > I've backported to gcc-10 branch (without any change to original
> > > > patches)
> > > > PR97969 and following PR98722 & PR98777 patches.
> > > >
> > > > Commits apply cleanly without changes.
> > > > Built and regression tested on:
> > > > * arm-none-eabi and
> > > > * aarch64-none-linux-gnu cross toolchains.
> > > >
> > > > There were no issues and no regressions (all OK).
> > > >
> > > > OK for backport to gcc-10 branch ?
> > >
> > > Sorry for delay with the answer due to my vacation.
> > >
> > > As the patches did not introduce new PRs I believe they are ok for gcc-10.
> >
> > Backported to gcc-10 branch. Thank you for your support.
> >
> 
> Hi,
> 
> I'm surprised to see many new errors on arm after the backport for PR98722
> See: https://people.linaro.org/~christophe.lyon/cross-validation/gcc/gcc-
> 10/r10-9881-g1791b11d9cae388ae18a768eeb96c998439c986a/report-build-
> info.html
> 
> Przemyslaw, Vladimir do you confirm r10-9881 has no such errors (new
> ICEs) on your side?

Apologies.

I've built and regtested before submitting backport yesterday.
I will check on my side and build one of your failing configurations.

Przemyslaw

> Thanks
> 
> > Kind regards
> > Przemyslaw
> >
> > > Thank you.
> > >
> > > >
> > > > Kind regards,
> > > > Przemyslaw Wirkus
> > > >
> > > > ---
> > > > commits I've backported:
> > > >
> > > > commit cf2ac1c30af0fa783c8d72e527904dda5d8cc330
> > > > Author: Vladimir N. Makarov <vmakarov@redhat.com>
> > > > Date:   Tue Jan 12 11:26:15 2021 -0500
> > > >
> > > >      [PR97969] LRA: Transform pattern `plus (plus (hard reg,
> > > > const), pseudo)`
> > > after elimination
> > > >
> > > > commit 4334b524274203125193a08a8485250c41c2daa9
> > > > Author: Vladimir N. Makarov <vmakarov@redhat.com>
> > > > Date:   Wed Jan 20 11:40:14 2021 -0500
> > > >
> > > >      [PR98722] LRA: Check that target has no 3-op add insn to
> > > > transform 2
> > > plus expression.
> > > >
> > > > commit 68ba1039c7daf0485b167fe199ed7e8031158091
> > > > Author: Vladimir N. Makarov <vmakarov@redhat.com>
> > > > Date:   Thu Jan 21 17:27:01 2021 -0500
> > > >
> > > >      [PR98777] LRA: Use preliminary created pseudo for in LRA
> > > > elimination
> > > subpass
> > > >
> > > > $ ./contrib/git-backport.py
> > > > cf2ac1c30af0fa783c8d72e527904dda5d8cc330
> > > > $ ./contrib/git-backport.py
> > > > 4334b524274203125193a08a8485250c41c2daa9
> > > > $ ./contrib/git-backport.py
> > > > 68ba1039c7daf0485b167fe199ed7e8031158091
> > > >
> > > >
> > > >> Richard.
> >

  reply	other threads:[~2021-06-03  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 10:43 Przemyslaw Wirkus
2021-01-18 12:50 ` Richard Biener
2021-01-18 15:06   ` Vladimir Makarov
2021-02-02 10:05     ` Przemyslaw Wirkus
2021-02-02 10:07       ` Richard Biener
2021-05-25  9:14         ` Przemyslaw Wirkus
2021-05-31 15:52           ` Vladimir Makarov
2021-06-02 22:30             ` Przemyslaw Wirkus
2021-06-03  8:45               ` Christophe Lyon
2021-06-03  8:54                 ` Przemyslaw Wirkus [this message]
2021-06-03  9:09                   ` Christophe Lyon
2021-06-03  9:16                     ` Przemyslaw Wirkus

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=PAXPR08MB66210BF964672378A2D3CD32E43C9@PAXPR08MB6621.eurprd08.prod.outlook.com \
    --to=przemyslaw.wirkus@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    --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).