public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: Richard Sandiford <Richard.Sandiford@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	nd <nd@arm.com>,	James Greenhalgh <James.Greenhalgh@arm.com>,
	Richard Earnshaw	<Richard.Earnshaw@arm.com>,
	Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: RE: [PATCH][GCC][AArch64] Add support for SVE stack clash probing [patch (2/7)]
Date: Tue, 09 Oct 2018 06:38:00 -0000	[thread overview]
Message-ID: <DB6PR0802MB2309682FA76E27034B546057FFE70@DB6PR0802MB2309.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <874le91qyx.fsf@arm.com>

Hi All,

I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.

OK for backport?

Thanks,
Tamar

> -----Original Message-----
> From: Richard Sandiford <richard.sandiford@arm.com>
> Sent: Friday, September 28, 2018 18:18
> To: Tamar Christina <Tamar.Christina@arm.com>
> Cc: gcc-patches@gcc.gnu.org; nd <nd@arm.com>; James Greenhalgh
> <James.Greenhalgh@arm.com>; Richard Earnshaw
> <Richard.Earnshaw@arm.com>; Marcus Shawcroft
> <Marcus.Shawcroft@arm.com>
> Subject: Re: [PATCH][GCC][AArch64] Add support for SVE stack clash probing
> [patch (2/7)]
> 
> Tamar Christina <Tamar.Christina@arm.com> writes:
> > Hi Richard,
> >
> > Here's the updated patch with all the feedback processed.
> >
> > I have also run the compile tests through with -mabi=ilp32 as well.
> >
> > Ok for trunk?
> 
> OK.  Thanks for your patience through all the reviews.
> 
> Richard

      reply	other threads:[~2018-10-09  6:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 12:19 Tamar Christina
2018-08-28 20:40 ` Richard Sandiford
2018-09-07 16:05   ` Tamar Christina
2018-09-11 15:20     ` Richard Sandiford
2018-09-20  9:27       ` Tamar Christina
2018-09-26  8:31         ` Tamar Christina
2018-09-27 10:14           ` Tamar Christina
2018-09-27 11:13             ` Richard Sandiford
2018-09-28 16:42               ` Tamar Christina
2018-09-28 17:18                 ` Richard Sandiford
2018-10-09  6:38                   ` Tamar Christina [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=DB6PR0802MB2309682FA76E27034B546057FFE70@DB6PR0802MB2309.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=James.Greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.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).