public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: bergner@linux.ibm.com
Cc: Vladimir Makarov <vmakarov@redhat.com>,
	Renlin Li <renlin.li@foss.arm.com>, 	Jeff Law <law@redhat.com>,
	gcc Patches <gcc-patches@gcc.gnu.org>,
		Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
		Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Subject: Re: [PATCH][LRA] Fix PR87899: r264897 cause mis-compiled native arm-linux-gnueabihf toolchain
Date: Wed, 14 Nov 2018 08:27:00 -0000	[thread overview]
Message-ID: <CAKdteOZk3RD9mCbx4qMzVAB0Cw9b_uX7NDR2FsaBkkqHj=wjQA@mail.gmail.com> (raw)
In-Reply-To: <d0fa1067-3099-86a6-f047-ad9bd68d03a1@linux.ibm.com>

On Tue, 13 Nov 2018 at 23:18, Peter Bergner <bergner@linux.ibm.com> wrote:
>
> On 11/13/18 4:09 PM, Vladimir Makarov wrote:
> > On 11/13/2018 10:53 AM, Peter Bergner wrote:
> >> I think with the above results, I think the patch is ready for review.
> >> I'm attaching the latest updated patch below.
> >>
> >> Again, this passed bootstrap and regtesting on powerpc64le-linux with
> >> no regressions.  Ok for mainline?
> >>
> > Ok, Peter.
>
> Ok, this is committed now.  Thanks for the review and thank you
> to everyone who helped debug and test the plethora of patches!!!
>

Thanks, on our side I can confirm the problems with the ARM bootstrap
is now fixed by your patch.

Christophe

> Peter
>
>
>

      reply	other threads:[~2018-11-14  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  4:34 Peter Bergner
2018-11-12 12:26 ` Renlin Li
2018-11-12 15:33   ` Peter Bergner
2018-11-12 16:26     ` Renlin Li
2018-11-12 20:25   ` Peter Bergner
2018-11-13 15:01     ` Renlin Li
2018-11-13 15:53       ` Peter Bergner
2018-11-13 22:09         ` Vladimir Makarov
2018-11-13 22:18           ` Peter Bergner
2018-11-14  8:27             ` Christophe Lyon [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='CAKdteOZk3RD9mCbx4qMzVAB0Cw9b_uX7NDR2FsaBkkqHj=wjQA@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=bergner@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@arm.com \
    --cc=law@redhat.com \
    --cc=renlin.li@foss.arm.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).