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: Fri, 24 Mar 2023 08:02:14 +0100 [thread overview]
Message-ID: <CAFiYyc1otdMA7a3UKMvOhJ4nuNtuBXYmr8EQgKCJgqU-6R2O5g@mail.gmail.com> (raw)
In-Reply-To: <ri6wn37tkat.fsf@suse.cz>
On Thu, Mar 23, 2023 at 7:05 PM Martin Jambor <mjambor@suse.cz> wrote:
>
> Hello,
>
> On Wed, Mar 22 2023, Richard Biener wrote:
> > 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.
>
> thanks.
>
> > Note the gcc-12 changes for the upcoming 12.3 need something similar
> > as most of the changes were backported.
>
> Like this?
Yes. Thanks,
Richard.
> Thanks,
>
> Martin
>
>
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> index d565c217..0854b83b 100644
> --- a/htdocs/gcc-12/changes.html
> +++ b/htdocs/gcc-12/changes.html
> @@ -1144,6 +1144,17 @@ are not listed here).</p>
> <p>Note: GCC 12.3 has not been released yet, so this section is a
> work-in-progress.</p>
>
> +<h3>Target Specific Changes</h3>
> +
> +<h3>x86-64</h3>
> +<ul>
> + <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>
> +
> +
> <p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=12.3">list
> of problem reports (PRs)</a> from GCC's bug tracking system that are
> known to be fixed in the 12.3 release. This list might not be
prev parent reply other threads:[~2023-03-24 7:02 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
2023-03-23 18:05 ` Martin Jambor
2023-03-24 7:02 ` Richard Biener [this message]
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=CAFiYyc1otdMA7a3UKMvOhJ4nuNtuBXYmr8EQgKCJgqU-6R2O5g@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).