From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A498E3858005; Thu, 28 Sep 2023 00:20:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A498E3858005 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1695860449; bh=XsdNHjVS3Z0zxzZ8cwCl99BdH7J9lYDS+I/5JQ05RY8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qV58N8i7IrGmKgabFVcX2WWgtvQgD/iciuPZO5tMFhWqbK+nMjdcdPUubgIhYGNMQ 0BAd2yLKQNn0Bv26TdvsWsKAd2SiXCkXH0DcuAEy1aqHwyF5EO+zpBglrjPQF3RAMs Q7j96c4hdV7ttF8CBm3Q+01CZlxu7Q+YA3U4DB+w= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111591] ppc64be: miscompilation with -mstrict-align / -O3 Date: Thu, 28 Sep 2023 00:20:48 +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: linkw at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status 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 Kewen Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gn= u.org Status|NEW |ASSIGNED --- Comment #15 from Kewen Lin --- (In reply to Richard Biener from comment #14) > (In reply to Kewen Lin from comment #13) > > Thanks again for the reduced test case and the information! > >=20 > > I tried to bisect it but encountered some build failures on _Float32 er= ror > > etc., through grepping the log I switched to start from r13-2887 (good)= to > > r13-7206 (bad). > >=20 > > The bisection shows the culprit commit is r13-3378-gf6c168f8c06047 whic= h was > > backported to GCC-12, it seems to match the observation new gcc-12 fail > > while gcc-11 pass. >=20 > Note this change likely triggers a latent issue but it might help analyzi= ng > the issue. Thanks for the hint! Yeah, I tried -fdisable-tree-esra and -fdisable-tree-s= ra, the failure is still there, I supposed that commit only takes effect when S= RA is enabled. I'll continue to investigate it. btw, I'm just starting two wee= ks vacation so may respond slowly.=