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 3D170385414A; Wed, 24 Aug 2022 18:43:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3D170385414A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1661366619;
	bh=Twj3isLQfI2zPMxUo2U56g/62UNzkvvXHbKp37Vjf8M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pkAuogVXckyi9EgFu/USsdzXetbc48QDNx+hxk3s0yO3/UMlZh7orT+OShsYm3Nez
	 ggcDIR4NUCBlE1YEqmAeHZM/I9qECH3DnQq3QCK/JmzkEDzvMyLjgA4QssZKRPJ2Yo
	 c6MM2sxfjCgB3Ei53DwcEjYdrGpLAC8uv1iX2pNA=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/106516] New test case gcc.dg/pr104992.c fails on
 power 10
Date: Wed, 24 Aug 2022 18:43:38 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106516-4-LpPqZShD4A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106516-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106516-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=3D106516

--- Comment #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #7)
> In this patch, I mainly
> followed the existing practice vect_int_mult (there are also some similar
> effective targets describing target vector support capability). With this
> way, if some other arches support this in future, target owners need to a=
dd
> their own conditions.

Yes, and those target maintainers will notice when they add the HW support =
and
then see this test case FAIL, just like we did on P10.=