From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B68AB385840F; Tue, 30 Jan 2024 03:05:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B68AB385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706583938; bh=LO1Mra+lq6cG0D3adE3IRdClNWnX+QallXProXQ+9QA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IwGZhljD2V0tAxQweqjKFOhByXvSAoGRz8s4RvOy5EmgBN1PDybh4xV9l/whzOm7/ u5cxX+WBXDc0voEA3ON/O91OfZ5vh+P0Rxar/A9D7FUhHiueYibBRllJMM33YhTnAn qS0+QkNrH66UBRGQevPVkcXhe7fdsBEZzAW2wsoY= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113652] [14 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450 Date: Tue, 30 Jan 2024 03:05:37 +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: 14.0 X-Bugzilla-Keywords: assemble-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.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=3D113652 --- Comment #6 from Kewen Lin --- I think this is related to r10-580-ge154242724b084 and this failure is expe= cted and a use error. With it applied, we don't always pass -many to assembler with CHECKING_P enabled. Actually compilers (gcc-13, gcc-12, gcc-11 or trunk) generate the = same assembly, but because gcc-11/gcc-12/gcc-13 is built with --checking=3Drelea= se by default which doesn't set CHECKING_P while trunk is built with --checking=3Dyes,extra by default which set CHECKING_P. So it causes the different behaviors so that further considered as regression unexpectedly. The issue should be gone if trunk gets released as gcc-14 or it's built with --checking=3Drelease. IMO Alan's commit aims to help to expose more and mor= e such unexpected use cases and users can fix them in place. As #c3 "PowerPC 7450 = (aka PowerPC G4) is only capable of -maltivec but not -mvsx", so it's unexpected= to have -mcpu=3D7450 meanwhile having -mvsx, could you check where the -mvsx c= omes from and fix it instead? Thanks! btw, a workaround option is to add -Wa,-many to restore the previous behavi= or that passing -many to assembler.=