public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: liuhongt <hongtao.liu@intel.com>
Cc: gcc-patches@gcc.gnu.org, crazylht@gmail.com, hjl.tools@gmail.com,
	ubizjak@gmail.com
Subject: Re: [PATCH] [x86] define builtins for "shared" avxneconvert-avx512bf16vl builtins.
Date: Fri, 18 Nov 2022 08:49:56 +0100	[thread overview]
Message-ID: <Y3c5JCpnW45HdcUr@tucnak> (raw)
In-Reply-To: <20221118014522.1989180-1-hongtao.liu@intel.com>

On Fri, Nov 18, 2022 at 09:45:22AM +0800, liuhongt via Gcc-patches wrote:
> This should fix incorrect error when call those builtin with
> -mavxneconvert and w/o -mavx512bf16 -mavx512vl.
> 
> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}
> Ready to push to trunk.
> 
> gcc/ChangeLog:
> 
> 	* config/i386/i386-builtins.cc (def_builtin): Hanlde "shared"

Just a nit: s/Hanlde/Handle/

> 	avx512bf16vl-avxneconvert builtins.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.target/i386/avxneconvert-1.c: New test.

	Jakub


  reply	other threads:[~2022-11-18  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  1:45 liuhongt
2022-11-18  7:49 ` Jakub Jelinek [this message]
2022-11-18  7:53   ` 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=Y3c5JCpnW45HdcUr@tucnak \
    --to=jakub@redhat.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hongtao.liu@intel.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).