From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6074D3858D28; Thu, 25 Aug 2022 12:01:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6074D3858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1661428912; bh=ZUwCxsqbpdeGli8ABuvsswzeJKXo5FRYdxKnkedGeKg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MdvtxCxVo2wMc8ITxwN42NsOfK2EOms9JslNvJcHZLZyIlZbOHY97hN44DV+qDac9 6M35WXtUSVNXEDGBmTmyIT3+jcRTSUa5iUETFx6+6WqRb3a8kxgDD8jeATGh4G8Nei ca6lh+G/9ZOQgCpYHR53Z+y9o7JEuwog/PJbTKRY= From: "bergner at gcc dot 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: Thu, 25 Aug 2022 12:01:52 +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: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 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=3D106736 --- Comment #3 from Peter Bergner --- (In reply to Kewen Lin from comment #2) > I wonder if we want to support types __vector_quad and __vector_pair with= out > MMA support (or supposed to be fixed with Power10 later). If no, we need = to > guard register_builtin_type under TARGET_MMA (TARGET_POWER10 later) for > those types. If yes, we may need to revisit its supports. 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 m= ight produce XOmode and OOmode usage. So basically, the "types" are limited to = MMA, but the opaque modes are not limited to MMA.=