From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 370853858D38; Thu,  9 Nov 2023 00:07:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 370853858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699488443;
	bh=uc7tRkHyWqWT8Kj6tHMDbRU+zZW2Bi2livTxIRrZB1U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=f97FcEbx3gskutsbZ7Yldo1QsNWrJ3uKW6lJh0575IBmTXz4sBUP0sa0fWCNCXm8r
	 xR5gSlWHPm4b3f9vzCkQ0VXObX75RZRl4PKdXrKx8I4ovDrenDm/aKNQAQ0p8FPcRn
	 ydW7I5xkc7sfbxbou7+TxXrVWdVuYzBsOnlYbU4w=
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/112415] [14 regression] Python 3.11
 miscompiled on HPPA with new RTL fold mem offset pass, since
 r14-4664-g04c9cf5c786b94
Date: Thu, 09 Nov 2023 00:07:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law 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: <bug-112415-4-WCj9IuzpYO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112415-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112415-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112415

--- Comment #26 from Jeffrey A. Law <law at gcc dot gnu.org> ---
As a compiler junkie, I tend to think compiler first until I can prove it
otherwise.  I wouldn't get too hung up on aliasing issues and such at this
point.

Do we already have a dump for the key function?  Presumably f-m-o doesn't
trigger *that* much.  And if this is triggering w/o LTO we can probably mov=
e to
cross debugging and analysis of those dump files and assembly code with and
without f-m-o enabled, narrowing our focus on the key function.=