public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Martin Jambor <jamborm@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 5e18cb8894845619ad2a362e5eee77c91cdc58ee
Date: Thu, 23 Mar 2023 17:36:25 +0000 (GMT)	[thread overview]
Message-ID: <20230323173625.2345D384841D@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  5e18cb8894845619ad2a362e5eee77c91cdc58ee (commit)
      from  e24f9ef56c11c69fc07bddf9a708ea2fc662f2b3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5e18cb8894845619ad2a362e5eee77c91cdc58ee
Author: Martin Jambor <mjambor@suse.cz>
Date:   Thu Mar 23 16:38:20 2023 +0100

    Add a note to gcc-13 changes that znver4 CPUs are supported

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 4fae1f7a..f8e9560c 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -530,6 +530,10 @@ a work-in-progress.</p>
     <code>-march=graniterapids</code>.
     The switch enables the AMX-FP16 and PREFETCHI ISA extensions.
   </li>
+  <li>GCC now supports AMD CPUs based on the <code>znver4</code> core
+    via <code>-march=znver4</code>.  The switch makes GCC consider
+    using 512 bit vectors when auto-vectorizing.
+  </li>
 </ul>
 
 <!-- <h3 id="mips">MIPS</h3> -->

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html | 4 ++++
 1 file changed, 4 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-03-23 17:36 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=20230323173625.2345D384841D@sourceware.org \
    --to=jamborm@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).