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 60B853858032; Thu, 16 Nov 2023 17:43:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 60B853858032
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700156593;
	bh=d8bbMiZE8rfaqAu20ADoO1BFaCcjOj9XRuzoxu0pVh0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=w5lmcqKErQ8bFldFF/edOJO4pxg+6pJYqdWDH8C412kcgWLo84tyHvsD+9gpqQ2OY
	 d3d84T2yxmRWRy8MMgv6H7D6ajizdAQA1DAbvxPyIBl/A1PUZMmjcaV2ztJK67lvZh
	 9ffxb8SC7gnhvAbWGPkHM3PHDXDBzPAVv62NhuoI=
From: "cvs-commit 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, 16 Nov 2023 17:43:10 +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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-DiPUK0pphN@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 #50 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John David Anglin <danglin@gcc.gnu.or=
g>:

https://gcc.gnu.org/g:d2934eb6ae92471484469d8ddd039eb34ef400b1

commit r14-5538-gd2934eb6ae92471484469d8ddd039eb34ef400b1
Author: John David Anglin <danglin@gcc.gnu.org>
Date:   Thu Nov 16 17:42:26 2023 +0000

    hppa: Revise REG+D address support to allow long displacements before
reload

    In analyzing PR rtl-optimization/112415, I realized that restricting
    REG+D offsets to 5-bits before reload results in very poor code and
    complexities in optimizing these instructions after reload.  The
    general problem is long displacements are not allowed for floating
    point accesses when generating PA 1.1 code.  Even with PA 2.0, there
    is a ELF linker bug that prevents using long displacements for
    floating point loads and stores.

    In the past, enabling long displacements before reload caused issues
    in reload.  However, there have been fixes in the handling of reloads
    for floating-point accesses.  This change allows long displacements
    before reload and corrects a couple of issues in the constraint
    handling for integer and floating-point accesses.

    2023-11-16  John David Anglin  <danglin@gcc.gnu.org>

    gcc/ChangeLog:

            PR rtl-optimization/112415
            * config/pa/pa.cc (pa_legitimate_address_p): Allow 14-bit
            displacements before reload.  Simplify logic flow.  Revise
            comments.
            * config/pa/pa.h (TARGET_ELF64): New define.
            (INT14_OK_STRICT): Update define and comment.
            * config/pa/pa64-linux.h (TARGET_ELF64): Define.
            * config/pa/predicates.md (base14_operand): Don't check
            alignment of short displacements.
            (integer_store_memory_operand): Don't return true when
            reload_in_progress is true.  Remove INT_5_BITS check.
            (floating_point_store_memory_operand): Don't return true when
            reload_in_progress is true.  Use INT14_OK_STRICT to check
            whether long displacements are always okay.=