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 145B13858C98; Sun, 24 Dec 2023 00:19:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 145B13858C98
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703377183;
	bh=hx+TfEG4Of/7C/LXfuR2XAWGpf3qymn/RiuromYFQh0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=IOLi8+ORe80V3UULiv+bAaTCEhqcMt682k1wgqeiI7lZB14tqEEyKS41CcqwlJIQS
	 U3rcvlGSiUNAFNbGXNjARj2cEOJBx0soUDQtlQhgMxZuDy3UM+HVU5ValKyqPLK6qR
	 jG8f8xriqcza+p/oK/JBBBj15FdVGtQQRQTuVb+8=
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113109] [14 Regression] g++ EH tests fail at
 execution time for cris-elf after r14-6674-g4759383245ac97
Date: Sun, 24 Dec 2023 00:19:26 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: EH, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: guojiufu 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-113109-4-mp6lAb5xnh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113109-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=3D113109

--- Comment #7 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #3)
>=20
> I'm "guessing" that the problem with the patch, is that anything any port
> stores through a pointer based on virtual_incoming_args_rtx before
> returning, is now eliminated.

Oh, yes, this is a possible place where that patch does not handle well.=