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 B5248384640E; Thu, 25 Apr 2024 08:00:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5248384640E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1714032045;
	bh=LhIvh3yb+NX+YbZtTyAVqH3T+X1lw9uFrdNHxce+x9M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=U6Mq3jb3TfBk7f0P0vDLNJuVaAo8Y7YUydbFbuHWgRbdi0b9nzm9B2PtTn5jPnspt
	 kXoR+cVEzVCT8gyfa27cQb0VulrzYWWHuBlhI9Fnz0w3HzlImAxbQ33gpLo+lgM9Ko
	 6io0+vU21Nn5n2/X3+vMfXb8jSQEHZgs71owsPzQ=
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114848] longarch: epilogue in _Unwind_RaiseException
 corrupts return value due to __builtin_eh_return
Date: Thu, 25 Apr 2024 08:00:45 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xry111 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: cc
Message-ID: <bug-114848-4-bElIjh15gr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114848-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=3D114848

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Hmm, AFAIK this should be already fixed with r14-6440?

I cannot reproduce it with r14-9823 but maybe it has regressed again in the
recent weeks.=