From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: [PATCH v2] gcc-13: aarch64: Document new cores
Date: Mon, 14 Nov 2022 16:03:54 +0100 [thread overview]
Message-ID: <CAAeLtUB=ExcndqbJ3nc876HWPy9vyjqpFzKhL7UtHD-b3yYu5g@mail.gmail.com> (raw)
In-Reply-To: <PAXPR08MB6926755706DD126B98CC88BC93059@PAXPR08MB6926.eurprd08.prod.outlook.com>
I squashed (so these are actually in the commit) and applied to master.
Philipp.
On Mon, 14 Nov 2022 at 15:56, Kyrylo Tkachov <Kyrylo.Tkachov@arm.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Philipp Tomsich <philipp.tomsich@vrull.eu>
> > Sent: Monday, November 14, 2022 2:54 PM
> > To: gcc-patches@gcc.gnu.org
> > Cc: Richard Sandiford <Richard.Sandiford@arm.com>; Kyrylo Tkachov
> > <Kyrylo.Tkachov@arm.com>; Philipp Tomsich <philipp.tomsich@vrull.eu>
> > Subject: [PATCH v2] gcc-13: aarch64: Document new cores
> >
> > Document the new cores added recently:
> > - ampere1a
> > - cortex-x1c
> > - cortex-a715
> > - cortex-x3
> > - neoverse-v2
>
> Thanks, but I think the patch doesn't reflect those yet 😉
> Ok with the entries added as discussed.
> Thanks,
> Kyirll
>
> >
> > Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
> > ---
> >
> > Changes in v2:
> > - Change capitalization of ARM to Arm.
> > - Add documentation for Cortex-X3 and Neoverse V2.
> >
> > htdocs/gcc-13/changes.html | 11 ++++++++++-
> > 1 file changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> > index 0daf921b..b82e198b 100644
> > --- a/htdocs/gcc-13/changes.html
> > +++ b/htdocs/gcc-13/changes.html
> > @@ -210,7 +210,16 @@ a work-in-progress.</p>
> > <!-- .................................................................. -->
> > <h2 id="targets">New Targets and Target Specific Improvements</h2>
> >
> > -<!-- <h3 id="aarch64">AArch64</h3> -->
> > +<h3 id="aarch64">AArch64</h3>
> > +<ul>
> > + <li>A number of new CPUs are supported through the <code>-
> > mcpu</code> and
> > + <code>-mtune</code> options (GCC identifiers in parentheses).
> > + <ul>
> > + <li>Ampere-1A (<code>ampere1a</code>).</li>
> > + <li>ARM Cortex-X1C (<code>cortex-x1c</code>).</li>
> > + <li>ARM Cortex-A715 (<code>cortex-a715</code>).</li>
> > + </ul>
> > +</ul>
> >
> > <h3 id="amdgcn">AMD Radeon (GCN)</h3>
> > <ul>
> > --
> > 2.34.1
>
prev parent reply other threads:[~2022-11-14 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 14:53 Philipp Tomsich
2022-11-14 14:56 ` Kyrylo Tkachov
2022-11-14 14:57 ` Philipp Tomsich
2022-11-14 15:03 ` Philipp Tomsich [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='CAAeLtUB=ExcndqbJ3nc876HWPy9vyjqpFzKhL7UtHD-b3yYu5g@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).