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 966773858D37; Tue,  3 Jan 2023 02:01:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 966773858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1672711317;
	bh=zwDDvCaK47vofweN6VdVM9CPWlbVDjCGPUQzMiBJJjE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=EL4gcbTI6eQZm7xsYqKc3dRB6lsbPas4kWspkK7n+W/FwL2Yu00S5yQHsnjrhVXts
	 ScfaJ4E4W+9hjhWIDVD22jnkpaeeMOP8yOFaFnNWTmuX1ipgjVDe57JVskiIiHKHj4
	 mZHa9i+DlmFSYTJqHRtSTwZMP9bd7c9r24NdCKVY=
From: "linkw 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: Tue, 03 Jan 2023 02:01:55 +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: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
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-pVAbEw2bRy@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 #15 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #14)
> W/ gcc 13.0.0 20221225 snapshot (g:febb58d28bfa4b544ec7ffec2d61f46d25205f=
f0)
> I still get this ICE when compiling
> gcc/testsuite/gcc.target/powerpc/mma-builtin-3.c:
>=20

Thanks for reporting, confirmed. The function rs6000_opaque_type_invalid_us=
e_p
only handles gassign, this failure shows another usage with asm, so we need=
 to
teach about gasm. Since it's for a new usage, I think it's better to have o=
ne
separated bug for it. Do you mind to file a new one?=20

Btw, excepting for this kind of asm usage, do you spot some others?=