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 E3D8A3858D1E; Thu,  9 Nov 2023 00:08:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E3D8A3858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699488539;
	bh=5astChoMsbxP5zQwXCFRNYwzKmlNO8wryEz+OHDKXg0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=MxfhcR/skBCCxX/0lkIZGVyImcKSK36H2MqzXdoni9Oiq9gAL5N7Ufylz0bU1exCj
	 3Jk5uHh3Mh8K4WRcn55lfflapDM19scv2F8w8Jb7lgqqGYv0mBGS9R1p0SC7J24Pl+
	 H0mVrXam3R+qdIXUY2CuFaXDfLlXWiEArEokCMp8=
From: "dave.anglin at bell dot net" <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:08:59 +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: dave.anglin at bell dot net
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-hyw1tAowKt@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 #27 from dave.anglin at bell dot net ---
On 2023-11-08 7:00 p.m., John David Anglin wrote:
> On 2023-11-08 6:51 p.m., sjames at gcc dot gnu.org wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112415
>>
>> --- Comment #23 from Sam James <sjames at gcc dot gnu.org> ---
>> (In reply to Andrew Pinski from comment #21)
>>> The other option to try is -fstack-reuse=3Dnone. There is definitely kn=
own
>>> issues with the code that coalesces stack variables together too (see PR
>>> 111843 for examples).
>> I had a good feeling about this but no, didn't help when applied to comp=
ile.o.
> At this point, I don't know whether this is a python or gcc bug. I scanne=
d for unions in compile.i
> that might be problematic but I didn't find anything obvious.
Note -no-strict-aliasing affects the inlining of compiler_visit_expr.=C2=A0=
 It is
not inlined with -no-strict-aliasing.=