public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Liu, Hongtao" <hongtao.liu@intel.com>
Cc: "Jiang, Haochen" <haochen.jiang@intel.com>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"ubizjak@gmail.com" <ubizjak@gmail.com>,
	 "burnus@net-b.de" <burnus@net-b.de>,
	"sandra@codesourcery.com" <sandra@codesourcery.com>
Subject: Re: [PATCH] i386: Add AVX10.1 related macros
Date: Wed, 10 Jan 2024 10:43:43 +0100	[thread overview]
Message-ID: <CAFiYyc34iC9RXNB=VqHtrgg3UeburR3YU_CrCu8QzLLVrSbs2g@mail.gmail.com> (raw)
In-Reply-To: <MW4PR11MB6762F68A2661E214A8EA2893E5692@MW4PR11MB6762.namprd11.prod.outlook.com>

On Wed, Jan 10, 2024 at 9:01 AM Liu, Hongtao <hongtao.liu@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Jiang, Haochen <haochen.jiang@intel.com>
> > Sent: Wednesday, January 10, 2024 3:35 PM
> > To: gcc-patches@gcc.gnu.org
> > Cc: Liu, Hongtao <hongtao.liu@intel.com>; ubizjak@gmail.com; burnus@net-
> > b.de; sandra@codesourcery.com
> > Subject: [PATCH] i386: Add AVX10.1 related macros
> >
> > Hi all,
> >
> > This patch aims to add AVX10.1 related macros for libgomp's request. The
> > request comes following:
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642025.html
> >
> > Ok for trunk?
> >
> > Thx,
> > Haochen
> >
> > gcc/ChangeLog:
> >
> >       PR target/113288
> >       * config/i386/i386-c.cc (ix86_target_macros_internal):
> >       Add __AVX10_1__, __AVX10_1_256__ and __AVX10_1_512__.
> > ---
> >  gcc/config/i386/i386-c.cc | 7 +++++++
> >  1 file changed, 7 insertions(+)
> >
> > diff --git a/gcc/config/i386/i386-c.cc b/gcc/config/i386/i386-c.cc index
> > c3ae984670b..366b560158a 100644
> > --- a/gcc/config/i386/i386-c.cc
> > +++ b/gcc/config/i386/i386-c.cc
> > @@ -735,6 +735,13 @@ ix86_target_macros_internal (HOST_WIDE_INT
> > isa_flag,
> >      def_or_undef (parse_in, "__EVEX512__");
> >    if (isa_flag2 & OPTION_MASK_ISA2_USER_MSR)
> >      def_or_undef (parse_in, "__USER_MSR__");
> > +  if (isa_flag2 & OPTION_MASK_ISA2_AVX10_1_256)
> > +    {
> > +      def_or_undef (parse_in, "__AVX10_1_256__");
> > +      def_or_undef (parse_in, "__AVX10_1__");
> I think this is not needed, others LGTM.

So __AVX10_1_256__ and __AVX10_1_512__ are redundant
with __AVX10_1__ and __EVEX512__, right?

> > +    }
> > +  if (isa_flag2 & OPTION_MASK_ISA2_AVX10_1_512)
> > +    def_or_undef (parse_in, "__AVX10_1_512__");
> >    if (TARGET_IAMCU)
> >      {
> >        def_or_undef (parse_in, "__iamcu");
> > --
> > 2.31.1
>

  reply	other threads:[~2024-01-10  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  7:34 Haochen Jiang
2024-01-10  7:58 ` Liu, Hongtao
2024-01-10  9:43   ` Richard Biener [this message]
2024-01-11  1:16     ` Liu, Hongtao
2024-01-11  8:18       ` Richard Biener
2024-01-12  2:54         ` Jiang, Haochen
2024-01-12  3:28           ` Hongtao Liu

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='CAFiYyc34iC9RXNB=VqHtrgg3UeburR3YU_CrCu8QzLLVrSbs2g@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=burnus@net-b.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=hongtao.liu@intel.com \
    --cc=sandra@codesourcery.com \
    --cc=ubizjak@gmail.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).