From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C902A393BC2C; Wed, 25 Nov 2020 21:12:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C902A393BC2C From: "meissner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96791] ICE in convert_mode_scalar, at expr.c:412 Date: Wed, 25 Nov 2020 21:12:45 +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: 11.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: meissner at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: bergner 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 21:12:45 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96791 --- Comment #22 from Michael Meissner --- When I wrote the original in power7 days, the intent was: If the user said -mcpu=3Dpower7 (for 32-bit) and did not explicitly set eit= her -mabi=3Daltivec or -mabi=3Dno-altivec, that -mabi=3Daltivec would be set automagically. If the user said -mcpu=3Dpower7 and did specify whether the altivec was set= , the compiler would honor that request. For 32-bit, I assume the problem may be our old friend TImode. Other parts= of the compiler, including the generic parts of block move assume that there m= ust be an integer mode as large as the largest non-vector mode. We don't provi= de TImode in 32-bit, and that leads us to have to disable IEEE 128-bit hardware support because we don't have a corresponding 128-bit integer for doing mov= es.=20 Before OPAQUE we did define OImode and XImode, but never enabled them, and = that prevented some ICEs where the machine independent parts did not bother to c= heck if the get integer mode size that is n-bits returned NULL.=