From: "Pop, Sebastian" <spop@amazon.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
Richard Earnshaw <richard.earnshaw@arm.com>,
"James Greenhalgh" <james.greenhalgh@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>, Sebastian Pop <sebpop@gmail.com>
Subject: gcc-7-arm vendor branch
Date: Thu, 10 Sep 2020 20:57:07 +0000 [thread overview]
Message-ID: <B9D48661-716E-4DFE-BA86-5D2E3DEB62BA@amazon.com> (raw)
Hi,
I would like to thank David Edelsohn for his help during the process of
getting Amazon’s contributions to GCC covered by an FSF copyright assignment.
As a first contribution, I would like to create a vendor branch for gcc-7
that will contain back-ported patches for Arm such as -moutline-atomics flag
and missing NEON intrinsics.
The branch will facilitate integration of these important changes in systems
such as Ubuntu 18.04 and Amazon Linux 2 that are still relying on gcc-7.
I will ask reviews and recommendations from Arm maintainers for the patches
to be integrated in the gcc-7-arm branch.
Thanks,
Sebastian
reply other threads:[~2020-09-10 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=B9D48661-716E-4DFE-BA86-5D2E3DEB62BA@amazon.com \
--to=spop@amazon.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=marcus.shawcroft@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=sebpop@gmail.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).