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 578933857C44; Thu,  9 Mar 2023 13:45:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 578933857C44
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678369513;
	bh=2mn1isxZeeJ/8gwgURVRj3z52o/S8+T1ie9OuAbC+pM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gISgUsMqTrvoCCaIgsLV3V0kBAKbf+PRupX62QQAVdL4ZesUFOWXomFqnQwae3a9C
	 wkokZtADWzKp6tKgKXHpmyl87pzBWqh+9BczkXPHXSonJ6+MwXHlMxOUyry3F1qQPM
	 f32br+xyFEybpsAAO+yjDAw1eZ1W17/Z6F2lZkNI=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/108999] Maybe LRA produce inaccurate hardware
 register occupancy information for subreg operand
Date: Thu, 09 Mar 2023 13:45:11 +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: 13.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108999-4-JaCwzP7III@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108999-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=3D108999

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.or=
g>:

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

commit r13-6551-ga6457974a1f443ab58d2334c02260299616c78b8
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Thu Mar 9 08:41:09 2023 -0500

    LRA: For clobbered regs use operand mode instead of the biggest mode

    LRA is too conservative in calculation of conflicts with clobbered regs=
 by
    using the biggest access mode.  This results in failure of possible reg
    coalescing and worse code.  This patch solves the problem.

            PR rtl-optimization/108999

    gcc/ChangeLog:

            * lra-constraints.cc (process_alt_operands): Use operand modes =
for
            clobbered regs instead of the biggest access mode.

    gcc/testsuite/ChangeLog:

            * gcc.target/aarch64/pr108999.c: New.=