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 A0B323858D3C; Fri,  2 Jun 2023 15:35:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A0B323858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685720157;
	bh=SXNlCcWbWQt9auV9RmcQiMBsam5nTaEl0CNnK1eV7U4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Pq+2gopWA1jN5JzK2e1bQRJS6utvSqPUMY1QHJeLeoPrt6ge6cDrW5jqZ+sEt9UMd
	 iaJTk1/c9Osw3llPifrHT5IEnBXjafF5L2iXPVdFR7NGNG6n/CkHmpuSmWGzJXMZQk
	 lBwzWngr6q1eICCI4YLE/DTz06lKnP4BKpVPKUhI=
From: "uweigand at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/101188] [postreload] Uses content of a
 clobbered register
Date: Fri, 02 Jun 2023 15:35:57 +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: 11.1.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uweigand 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-101188-4-VqDppHotGm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-101188-4@http.gcc.gnu.org/bugzilla/>
References: <bug-101188-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=3D101188

--- Comment #14 from Ulrich Weigand <uweigand at gcc dot gnu.org> ---
(In reply to Georg-Johann Lay from comment #13)
> Also I don't have a test case for your scenario.  I can reproduce the bug
> back to v5 on avr and maybe it is even older.  As it appears, this PR lead
> to no hickups on any other target, so for now I'd like to keep the fix
> restricted to what I can test.

I agree that your patch looks correct and unlikely to cause any new problem=
s,
so I won't object to it being committed.  I just wanted to point out that it
might not be a complete fix.=