public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114848] loongarch: epilogue in _Unwind_RaiseException corrupts return value due to __builtin_eh_return
Date: Thu, 25 Apr 2024 08:11:44 +0000 [thread overview]
Message-ID: <bug-114848-4-WQKqG2lnWZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114848-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114848
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|longarch: epilogue in |loongarch: epilogue in
|_Unwind_RaiseException |_Unwind_RaiseException
|corrupts return value due |corrupts return value due
|to __builtin_eh_return |to __builtin_eh_return
--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Xi Ruoyao from comment #1)
> > 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.
>
> Oh I only tested gcc 13.2.0. If it is fixed you can close it.
Hmm it looks like we need a backport to releases/gcc-13 (and 12?)
I thought the bug was introduced by my shrink-wrap change (r14-545) so I didn't
proposed a backport. But it seems I was wrong and the bug exists even before
r14-545.
next prev parent reply other threads:[~2024-04-25 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 7:45 [Bug target/114848] New: longarch: " pinskia at gcc dot gnu.org
2024-04-25 8:00 ` [Bug target/114848] " xry111 at gcc dot gnu.org
2024-04-25 8:04 ` pinskia at gcc dot gnu.org
2024-04-25 8:11 ` xry111 at gcc dot gnu.org [this message]
2024-04-25 8:21 ` [Bug target/114848] loongarch: " pinskia at gcc dot gnu.org
2024-04-27 9:05 ` chenglulu at loongson dot cn
2024-04-30 1:09 ` cvs-commit at gcc dot gnu.org
2024-04-30 1:11 ` cvs-commit at gcc dot gnu.org
2024-04-30 1:20 ` xry111 at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-114848-4-WQKqG2lnWZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).