From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id F2EBF3858414; Tue,  9 Jan 2024 07:30:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F2EBF3858414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704785446;
	bh=4Ry7D117Eyv+JK45y/hrsxiI0DhFhnccL+Fj1V6EBbU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rWlMpAyXyW5eD4EYsPk1qHZNnC4bA9cC+0jrCstgSQkqabIjIka9FWbCKZtUCWQg7
	 b3C7z6yTnbWrAcvsNPSa5iO/C3Mpoqf9HmibValWvKkSZISiT7aG1judtsLVpK0Dzf
	 iY3NkBdrOSaqc94P8F5NZ0+axyHg2NZcJkpXXZks=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haochen.jiang at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113288-4-jn1kD3859z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113288-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113288-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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
>=20
> There is not #define for -mavx10.1-256 and -mavx10.1-512
>=20
> By contrast, there is one for, e.g.,
>=20
> __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 previ=
ous
design but get obsoleted at the end. Let me see if we need something like t=
hat.

> __AMX_FP16__ and -mamx-fp16
> etc.=