From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 101D43858CDA; Mon, 29 May 2023 01:29:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 101D43858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685323759; bh=C22PTJslGv3UtgofdzFX1ReZUr+QRSmzf7HnwxzO70E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MAeKeEbgVljaXF+hKLtWT3S74KJ8ltYTdz11/lbh8wDTtErk5FGSiTD97K8lCRyAq Awj1AaXL+P2vzj59Db/hYwr7gDnjYyeypf3mu1Z2PhJ40fy5578hG2b7g9K1Zony+w ae9vNg/CnBAY7Hd18/IjqYUa6+8vIhb28v4RBjGI= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109987] ICE in in rs6000_emit_le_vsx_store on ppc64le with -Ofast -mno-power8-vector Date: Mon, 29 May 2023 01:29:18 +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: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status everconfirmed keywords cc cf_reconfirmed_on 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=3D109987 Kewen Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |ice-on-valid-code CC| |bergner at gcc dot gnu.org, | |linkw at gcc dot gnu.org, | |segher at gcc dot gnu.org Last reconfirmed| |2023-05-29 --- Comment #1 from Kewen Lin --- Confirmed, it's similar to what the issue was found in PR103627 #c4, previo= usly I made a patch to make MMA feature require power9-vector, see https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587310.html. But Se= gher thought power9-vector is a workaround option, we should make it go away, so just guard it under vsx, see his comment https://gcc.gnu.org/pipermail/gcc-patches/2022-January/589303.html. Unfortunately this issue is specified another workaround option -mno-power8-vector, I think we probably need to put -mpower{8,9}-vector rem= oval in a high priority.=