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 5FBEB3858C2C; Wed,  8 Nov 2023 19:07:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5FBEB3858C2C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699470470;
	bh=RViQEPtAuJCoCrmsx80UlUKMORCNGPiHqE60CR9jRRA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=bOMKKEAJIyyOJejf4VmVVi9oFLaXIdKvSH1R93bIq7Z/LJBQM1hXtyY3Q4bLY/8AD
	 xHZQx8SvCEYNBPrKjZel6pnstiGyOVN9ipvMc4cvfZU+3xCDWOVOGTBamaDtj3wnNu
	 kxMl2PB1oS3pevvXZrYKey+8RJIQhfe2AEV/sMB8=
From: "pinskia 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: Wed, 08 Nov 2023 19:07:49 +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: pinskia 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-8wWzLOzf3e@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 #18 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I wonder if -fno-strict-aliasing works around the issue too?
I get the feeling that `fold mem offset pass` allows the aliasing code to h=
ave
a better time with the offset and that might be expose more aliasing issues.

The other thing to try is add `-fno-schedule-insns2 -fno-schedule-insns`
instead of `-fno-strict-aliasing` as the scheduler is normally where the
aliasing issues are exposed on the RTL level ...=