public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114846] powerpc: epilogue in _Unwind_RaiseException corrupts return value due to __builtin_eh_return
Date: Thu, 25 Apr 2024 21:37:09 +0000 [thread overview]
Message-ID: <bug-114846-4-GVs3aD93HQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114846-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114846
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #2)
> As https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114843#c8, we may need some
> similar handling like r14-6440-g4b421728289e6f.
Note rs6000_emit_epilogue mostly handles eh_returns so it might not be as hard
as other targets.
next prev parent reply other threads:[~2024-04-25 21:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 7:34 [Bug target/114846] New: " pinskia at gcc dot gnu.org
2024-04-25 9:23 ` [Bug target/114846] " linkw at gcc dot gnu.org
2024-04-25 9:25 ` linkw at gcc dot gnu.org
2024-04-25 21:37 ` pinskia at gcc dot gnu.org [this message]
2024-04-29 5:20 ` linkw at gcc dot gnu.org
2024-04-29 9:04 ` linkw at gcc dot gnu.org
2024-05-14 8:49 ` linkw at gcc dot gnu.org
2024-05-29 2:15 ` cvs-commit at gcc dot gnu.org
2024-05-29 2:33 ` linkw at gcc dot gnu.org
2024-05-29 12:30 ` bergner at gcc dot gnu.org
2024-05-29 12:50 ` linkw at gcc dot gnu.org
2024-06-21 19:53 ` bergner at gcc dot gnu.org
2024-06-23 19:42 ` segher at gcc dot gnu.org
2024-06-24 1:43 ` cvs-commit at gcc dot gnu.org
2024-06-24 1:45 ` cvs-commit at gcc dot gnu.org
2024-06-24 1:46 ` cvs-commit at gcc dot gnu.org
2024-06-24 1:49 ` cvs-commit at gcc dot gnu.org
2024-06-24 3:46 ` linkw at gcc dot gnu.org
2024-06-24 3:50 ` linkw 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-114846-4-GVs3aD93HQ@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).