From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D81B23858414; Tue, 9 Jan 2024 07:54:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D81B23858414 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704786869; bh=qx/ke6fAqdrUy0Mg9ol5SsYkm9XQy2YoCAuUkCsLwLg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gqKkYqPbVDZN1qb7dF10LkgqlEq2QwtWhMIUbjuGwil7mkSn5O87z9JCLNtZJwtAq 5v0cog9b40JB62jlpPTJEegusfwG2G3Aa9pWQRXzcogGjVGhkWzWFYTLrctCJoQkj0 X0lChNrN3U4ALUX2x5Ljhtk16NN7S+ncZLYzxzNE= From: "haochen.jiang at intel dot com" 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:54:29 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113288 --- Comment #3 from Haochen Jiang --- Adding them are quite straightforward. But I am not quite sure how the whole libgomp patch works. Is the patch attempt to check whether it is a perfect match for each ISA detected from a hardware? If that is the case, we need them to be added. BT= W, under this scenario, no need to add an if clause for macro __EVEX512__ and __EVEX256__ in that patch since those two are not true ISAs.=