From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D37BB38618F3; Fri, 15 Dec 2023 10:23:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D37BB38618F3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1702635832; bh=TIUnbtQeC8oMwVaCXvrnuPvNFiH2wUsBy0blgPxtm0s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mb77rzjVugord4q+0aZ/A66jqamC/0D3Q3FX7DRFdAMoJEOENGb02hE6wWiTpAXfz 1NinKBb8D0zxpLcuGrwMntMc7U6H8iI4iln5TfMchloqYojwym8iAvoD1hz5OdPsDY fLY/0HrjFyMAywDOk/lWiqUUG57/yd6dPoG3UTZM= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111591] ppc64be: miscompilation with -mstrict-align / -O3 Date: Fri, 15 Dec 2023 10:23: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.2.0 X-Bugzilla-Keywords: needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED 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: 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=3D111591 --- Comment #39 from Richard Biener --- (In reply to Kewen Lin from comment #38) > I found this has been marked as resolved but it seems that the patch in > comment #34 hasn't been pushed, is it intended? or did I miss something t= hat > one commit was pushed but wasn't associated to this PR? Yes, that was intended - the patch is not necessary, there's no bug on the = TBAA side. I understand that highway itself is now fine (for whatever reason) a= nd the reduced testcase invokes undefined behavior.=