From: Jan Hubicka <hubicka@ucw.cz>
To: Hongtao Liu <crazylht@gmail.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com,
hongjiu.lu@intel.com, "Zhang, Annita" <annita.zhang@intel.com>
Subject: Re: Disable FMADD in chains for Zen4 and generic
Date: Wed, 17 Jan 2024 18:29:43 +0100 [thread overview]
Message-ID: <ZagOh-eirRyumB_X@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAMZc-bwmXQ_+GRTwT8zN-8qObBR13r-s22DASMRZtkuKjSY27g@mail.gmail.com>
> Can we backport the patch(at least the generic part) to
> GCC11/GCC12/GCC13 release branch?
Yes, the periodic testers has took the change and as far as I can tell,
there are no surprises.
Thanks,
Honza
> > > >
> > > > /* X86_TUNE_AVOID_512FMA_CHAINS: Avoid creating loops with tight 512bit or
> > > > smaller FMA chain. */
> > >
> > >
> > >
> > > --
> > > BR,
> > > Hongtao
>
>
>
> --
> BR,
> Hongtao
prev parent reply other threads:[~2024-01-17 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:37 Jan Hubicka
2023-12-12 15:01 ` Richard Biener
2023-12-12 16:48 ` Jan Hubicka
2023-12-12 17:08 ` Alexander Monakov
2023-12-12 23:56 ` Hongtao Liu
2023-12-13 16:03 ` Jan Hubicka
2024-01-08 3:16 ` Hongtao Liu
2024-01-17 17:29 ` Jan Hubicka [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=ZagOh-eirRyumB_X@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=annita.zhang@intel.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongjiu.lu@intel.com \
--cc=hongtao.liu@intel.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).