From: "Koval, Julia" <julia.koval@intel.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Kirill Yukhin <kirill.yukhin@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH][i386,AVX] Enable VBMI2 support [5/7]
Date: Tue, 12 Dec 2017 17:06:00 -0000 [thread overview]
Message-ID: <4E89A029A0F8D443B436A5167BA3C53F8A454316@IRSMSX151.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1712121133180.6587@anthias.pfeifer.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Here is the patch to update these files with my contributions. Ok for trunk?
Thanks,
Julia
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Gerald Pfeifer
> Sent: Tuesday, December 12, 2017 11:34 AM
> To: Koval, Julia <julia.koval@intel.com>
> Cc: Kirill Yukhin <kirill.yukhin@gmail.com>; gcc-patches@gcc.gnu.org
> Subject: RE: [PATCH][i386,AVX] Enable VBMI2 support [5/7]
>
> On Tue, 12 Dec 2017, Koval, Julia wrote:
> > Looks good. How to put it there(sorry, noob question)?
>
> Does https://gcc.gnu.org/about.html help? If not, let me know
> and I'll work with you (and update those docs on the way).
>
> Of course, even if things work for you, any suggestions on how
> to improve this little page are very welcome. :)
>
> Gerald
[-- Attachment #2: patch --]
[-- Type: application/octet-stream, Size: 715 bytes --]
Index: htdocs/gcc-8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.22
diff -r1.22 changes.html
32a33,34
> <li>The Cilk+ extensions to the C and C++ languages were removed from
> GCC.</li>
186a189,194
> <li>GCC now supports the Intel CPU named Cannonlake through
> -march=cannonlake. The switch enables the AVX512VBMI, AVX512IFMA and SHA
> ISA extensions.</li>
> <li>GCC now supports the Intel CPU named and Icelake through -march=icelake.
> The switch enables the AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ,
> AVX512BITALG, RDPID and AVX512VPOPCNTDQ ISA extensions.</li>
next prev parent reply other threads:[~2017-12-12 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:05 Koval, Julia
2017-12-03 17:51 ` Gerald Pfeifer
2017-12-04 7:19 ` Koval, Julia
2017-12-09 13:49 ` Gerald Pfeifer
2017-12-12 9:05 ` Koval, Julia
2017-12-12 10:34 ` Gerald Pfeifer
2017-12-12 17:06 ` Koval, Julia [this message]
2017-12-12 22:18 ` Gerald Pfeifer
2017-10-24 10:16 Koval, Julia
2017-11-28 18:09 ` Kirill Yukhin
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=4E89A029A0F8D443B436A5167BA3C53F8A454316@IRSMSX151.ger.corp.intel.com \
--to=julia.koval@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=kirill.yukhin@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).