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 A3A3938515D8; Fri, 26 Aug 2022 19:06:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A3A3938515D8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1661540774;
	bh=83bOeGeBZ+MDl84LMt4DBkaYDNjp5EfqPNNNasX3K3U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PdZfcWFbOce0oBNGxlgMLOe5sHclRffXbr4yhohkLOoJ5x6LWpwfZBEV3FLw28ys+
	 +sYr82Hc+b5ASwn01E45ka8B6q47f3FHpjTQQWZQSY37JPbAPyrAnhUvQpUhN4Fv+A
	 yTQrR4LKR3EoSN7aSiO/ujqUAp9U7dduI5Z5vjNE=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106736] [13 Regression] ICE in gen_movxo, at
 config/rs6000/mma.md:333
Date: Fri, 26 Aug 2022 19:06:14 +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: 13.0
X-Bugzilla-Keywords: ice-on-invalid-code
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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106736-4-BwnQr8Tm7P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106736-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=3D106736

--- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #3)
> No, the __vector_quad and __vector_pair types should only be used for MMA
> support.  That's not to say in the future that some other different types
> might produce XOmode and OOmode usage.  So basically, the "types" are
> limited to MMA, but the opaque modes are not limited to MMA.

So you may wonder about the above given my latest reply in Comment #5! :-) =
 I
meant to say that the user should only be able to use the __vector_pair and
__vector_quad types when MMA is enabled.  That might be because they used
-mmma/-mcpu=3Dpower10 or because they're using a pragma/target attribute to
enable MMA for one specific function.

...and we actually do catch the illegal usage, but how we can fail graceful=
ly
instead of an ICE is what we need to figure out.  Maybe similar to your
PR103353, we just need the mov[xo]o patterns to succeed temporarily so we c=
an
fail gracefully later?=