From: Richard Biener <richard.guenther@gmail.com>
To: "Pop, Sebastian" <spop@amazon.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Subject: Re: [gcc-7-arm] Backport -moutline-atomics flag
Date: Wed, 11 Nov 2020 15:44:34 +0100 [thread overview]
Message-ID: <CAFiYyc29v+yTg96EDcMCPCuCRfoBhrspw6Rxc8E=iYU55ApDGA@mail.gmail.com> (raw)
In-Reply-To: <73A2205A-8D58-461C-BD18-1C6AA1ED8716@amazon.com>
On Thu, Sep 24, 2020 at 4:59 PM Pop, Sebastian <spop@amazon.com> wrote:
>
> Thanks Richard for your recommendations.
> I am still discussing with Kyrill about a good name for the branch.
> Once we agree on a name we will commit the patches to that branch.
Any update here? Are those patches in production at Amazon?
I now see refs/vendors/AWS/heads/Arm64/gcc-7-branch
Thanks,
Richard.
> Sebastian
>
> On 9/24/20, 4:10 AM, "Richard Biener" <richard.guenther@gmail.com> wrote:
>
> On Fri, Sep 11, 2020 at 12:38 AM Pop, Sebastian via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > Hi,
> >
> > the attached patches are back-porting the flag -moutline-atomics to the gcc-7-arm vendor branch.
> > The flag enables a very important performance optimization for N1-neoverse processors.
> > The patches pass bootstrap and make check on Graviton2 aarch64-linux.
> >
> > Ok to commit to the gcc-7-arm vendor branch?
>
> Given the branch doesn't exist yet can you eventually push this series to
> a user branch (or a amazon vendor branch)?
>
> You failed to CC arm folks so your mail might have been lost in the noise.
>
> Thanks,
> Richard.
>
> > Thanks,
> > Sebastian
> >
>
next prev parent reply other threads:[~2020-11-11 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 14:59 Pop, Sebastian
2020-11-11 14:44 ` Richard Biener [this message]
2020-11-11 15:23 ` Pop, Sebastian
-- strict thread matches above, loose matches on Subject: below --
2020-09-10 22:35 Pop, Sebastian
2020-09-24 9:09 ` Richard Biener
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='CAFiYyc29v+yTg96EDcMCPCuCRfoBhrspw6Rxc8E=iYU55ApDGA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=spop@amazon.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).