From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 75F473858D3C; Sat, 23 Dec 2023 17:25:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 75F473858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1703352334; bh=9noHyCIcddpIiqXYxnNsm0iZtMnlJqS9OExvUewWqLE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ui1bNE6V6FdYGWBqg13awCiSBO67N9oJcqo8pU7VFTIZ7XZVgnrSsQ5J5EG9bLv4Y RZRH/9D/XyBEjVhvchhOk1XU2rBAuAJD8BAZPFrzOYP3KgVVhmqVymfHVQlW+vPTT1 owhyawMCWoadc/CRwpME1zxYJkUJdIy251t/2hig= From: "pinskia at gcc dot 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: Sat, 23 Dec 2023 17:25:34 +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: 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113109 --- Comment #6 from Andrew Pinski --- So I did a quick audit of the EH_RETURN_HANDLER_RTX and most are registers rather than a memory location . And the ones which were memory locations u= sed either frame or stack pointer directly which seemed to not to be removed. I= had originally was going to record my findings but then I saw the volatile for = pa risc and deleted what I had wrote up.=