From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "ubizjak@gmail.com" <ubizjak@gmail.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support
Date: Fri, 27 Oct 2023 02:54:42 +0000 [thread overview]
Message-ID: <SA1PR11MB594602217D64CA42F490E80CECDCA@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SA1PR11MB59461115FE2C02E59C985D14ECDCA@SA1PR11MB5946.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Jiang, Haochen <haochen.jiang@intel.com>
> Sent: Friday, October 27, 2023 10:52 AM
> To: Jiang, Haochen <haochen.jiang@intel.com>; gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao <hongtao.liu@intel.com>; ubizjak@gmail.com; Gerald Pfeifer
> <gerald@pfeifer.com>
> Subject: RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and
> march support
>
> > -----Original Message-----
> > From: Gcc-patches <gcc-patches-
> > bounces+haochen.jiang=intel.com@gcc.gnu.org> On Behalf Of Haochen
> > bounces+Jiang
> > via Gcc-patches
> > Sent: Monday, July 17, 2023 11:34 AM
> > To: gcc-patches@gcc.gnu.org
> > Cc: Liu, Hongtao <hongtao.liu@intel.com>; ubizjak@gmail.com
> > Subject: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and
> > march support
> >
> > Hi all,
> >
> > This patch adds documentation to wwwdocs to mention the recent
> > introduction of Intel new ISA and march.
> >
> > Ok for trunk?
>
> I will commit the patch next Monday if there is no objection.
Sorry for the disturb since I find the wrong mail to reply because they
are too similar.
>
> Thx,
> Haochen
>
> >
> > BRs,
> > Haochen
> >
> > ---
> > htdocs/gcc-13/changes.html | 4 ++++
> > htdocs/gcc-14/changes.html | 34
> > +++++++++++++++++++++++++++++++++-
> > 2 files changed, 37 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> > index 39414e18..68e8c5cc 100644
> > --- a/htdocs/gcc-13/changes.html
> > +++ b/htdocs/gcc-13/changes.html
> > @@ -593,6 +593,10 @@ You may also want to check out our
> > </li>
> > <li>GCC now supports the Intel CPU named Granite Rapids through
> > <code>-march=graniterapids</code>.
> > + The switch enables the AMX-FP16, PREFETCHI ISA extensions.
> > + </li>
> > + <li>GCC now supports the Intel CPU named Granite Rapids D through
> > + <code>-march=graniterapids-d</code>.
> > The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA
> > extensions.
> > </li>
> > <li>GCC now supports AMD CPUs based on the <code>znver4</code> core
> > diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> > index
> > 3f797642..dad1ba53 100644
> > --- a/htdocs/gcc-14/changes.html
> > +++ b/htdocs/gcc-14/changes.html
> > @@ -108,7 +108,39 @@ a work-in-progress.</p>
> >
> > <!-- <h3 id="avr">AVR</h3> -->
> >
> > -<!-- <h3 id="x86">IA-32/x86-64</h3> -->
> > +<h3 id="x86">IA-32/x86-64</h3>
> > +<ul>
> > + <li>New ISA extension support for Intel AVX-VNNI-INT16 was added.
> > + AVX-VNNI-INT16 intrinsics are available via the <code>-
> > mavxvnniint16</code>
> > + compiler switch.
> > + </li>
> > + <li>New ISA extension support for Intel SHA512 was added.
> > + SHA512 intrinsics are available via the <code>-msha512</code>
> > + compiler switch.
> > + </li>
> > + <li>New ISA extension support for Intel SM3 was added.
> > + SM3 intrinsics are available via the <code>-msm3</code>
> > + compiler switch.
> > + </li>
> > + <li>New ISA extension support for Intel SM4 was added.
> > + SM4 intrinsics are available via the <code>-msm4</code>
> > + compiler switch.
> > + </li>
> > + <li>GCC now supports the Intel CPU named Arrow Lake through
> > + <code>-march=arrowlake</code>.
> > + Based on Alder Lake, the switch further enables the AVX-IFMA,
> > + AVX-VNNI-INT8, AVX-NE-CONVERT and CMPccXADD ISA extensions.
> > + </li>
> > + <li>GCC now supports the Intel CPU named Arrow Lake S through
> > + <code>-march=arrowlake-s</code>.
> > + Based on Arrow Lake, the switch further enables the
> > + AVX-VNNI-INT16,
> > SHA512,
> > + SM3 and SM4 ISA extensions.
> > + </li>
> > + <li>GCC now supports the Intel CPU named Lunar Lake through
> > + <code>-march=lunarlake</code>.
> > + Lunar Lake is based on Arrow Lake S.
> > + </li>
> > +</ul>
> >
> > <!-- <h3 id="mips">MIPS</h3> -->
> >
> > --
> > 2.31.1
next prev parent reply other threads:[~2023-10-27 2:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 3:33 Haochen Jiang
2023-07-17 6:40 ` Richard Biener
2023-10-27 2:51 ` Jiang, Haochen
2023-10-27 2:54 ` Jiang, Haochen [this message]
2023-11-25 11:29 ` Gerald Pfeifer
2023-11-27 1:50 ` Jiang, Haochen
2023-12-13 5:44 ` Gerald Pfeifer
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=SA1PR11MB594602217D64CA42F490E80CECDCA@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ubizjak@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).