public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. ecfa9ea39503ea32fc7be39b3adc247725800729
Date: Tue, 27 Apr 2021 11:46:43 +0000 (GMT)	[thread overview]
Message-ID: <20210427114643.70559383303D@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  ecfa9ea39503ea32fc7be39b3adc247725800729 (commit)
      from  2d8a1a96aa266e29040e435fb592bcfcb352110e (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 ecfa9ea39503ea32fc7be39b3adc247725800729
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Apr 27 11:46:23 2021 +0000

    mention x86-64-vX micro-architecture levels

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 63a668b3..4bdae272 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -691,6 +691,10 @@ You may also want to check out our
   <li>GCC now supports AMD CPUs based on the <code>znver3</code> core
     via <code>-march=znver3</code>.
   </li>
+  <li>GCC now supports micro-architecture levels defined in the x86-64 psABI
+    via <code>-march=x86-64-v2</code>, <code>-march=x86-64-v3</code> and
+    <code>-march=x86-64-v4</code>.
+  </li>
 </ul>
 
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-04-27 11:46 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=20210427114643.70559383303D@sourceware.org \
    --to=doko@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).