public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113288] [i386] Missing #define for -mavx10.1-256 and -mavx10.1-512
Date: Tue, 09 Jan 2024 07:30:46 +0000	[thread overview]
Message-ID: <bug-113288-4-jn1kD3859z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113288-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113288

--- Comment #1 from Haochen Jiang <haochen.jiang at intel dot com> ---
(In reply to Tobias Burnus from comment #0)
> As noted in
> https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642025.html
> 
> There is not #define for -mavx10.1-256 and -mavx10.1-512
> 
> By contrast, there is one for, e.g.,
> 
> __AVX10_512BIT__ and "avx10-max-512bit"
> __AVX10_1__ and "avx10.1"

I think both of these two are also not on current trunk, they are the previous
design but get obsoleted at the end. Let me see if we need something like that.

> __AMX_FP16__ and -mamx-fp16
> etc.

  reply	other threads:[~2024-01-09  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09  7:23 [Bug target/113288] New: " burnus at gcc dot gnu.org
2024-01-09  7:30 ` haochen.jiang at intel dot com [this message]
2024-01-09  7:49 ` [Bug target/113288] " liuhongt at gcc dot gnu.org
2024-01-09  7:54 ` haochen.jiang at intel dot com
2024-01-09  8:43 ` burnus at gcc dot gnu.org
2024-01-12  7:56 ` cvs-commit at gcc dot gnu.org
2024-01-12  7:57 ` haochen.jiang at intel dot com
2024-04-08  8:18 ` liuhongt at gcc dot gnu.org

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=bug-113288-4-jn1kD3859z@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).