From: Richard Biener <richard.guenther@gmail.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [wwwdocs] Document support for znver4 in gcc-13/changes.html
Date: Wed, 22 Mar 2023 11:11:14 +0100 [thread overview]
Message-ID: <CAFiYyc14SO9O8EVsTwN77JWe4CwnaXHLY+MRuhrGL9V=DT6d=A@mail.gmail.com> (raw)
In-Reply-To: <ri68rfpx5z3.fsf@suse.cz>
On Tue, Mar 21, 2023 at 8:25 PM Martin Jambor <mjambor@suse.cz> wrote:
>
> Hello,
>
> is the following item documenting that gcc13 can generate code for Zen 4
> OK for the changes.html file on the web?
OK. Note the gcc-12 changes for the upcoming 12.3 need something similar
as most of the changes were backported.
Richard.
> Thanks,
>
> Martin
>
>
> 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> -->
next prev parent reply other threads:[~2023-03-22 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:24 Martin Jambor
2023-03-22 10:11 ` Richard Biener [this message]
2023-03-23 18:05 ` Martin Jambor
2023-03-24 7:02 ` Richard Biener
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='CAFiYyc14SO9O8EVsTwN77JWe4CwnaXHLY+MRuhrGL9V=DT6d=A@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
/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).