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/114843] AArch64: Wrong Register Reload in _Unwind_RaiseException causes corrupt return value on _URC_END_OF_STACK Date: Thu, 25 Apr 2024 07:10:06 +0000 [thread overview] Message-ID: <bug-114843-4-soVx0Y3CEm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114843-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114843 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2024-04-25 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed reduced runtime self contained testcase: ``` __attribute__((noipa)) int f(int *a, long offset, void *handler) { if (*a == 5) return 5; __builtin_eh_return (offset, handler); } int main() { int t = 5; if (f(&t, 0, 0) != 5) __builtin_abort(); } ```
next prev parent reply other threads:[~2024-04-25 7:10 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-25 6:31 [Bug libgcc/114843] New: " hugo at algoriddim dot com 2024-04-25 6:32 ` [Bug libgcc/114843] " hugo at algoriddim dot com 2024-04-25 6:45 ` [Bug target/114843] " pinskia at gcc dot gnu.org 2024-04-25 6:53 ` pinskia at gcc dot gnu.org 2024-04-25 7:10 ` pinskia at gcc dot gnu.org [this message] 2024-04-25 7:14 ` [Bug target/114843] aarch64: epoligue in _Unwind_RaiseException corrupts return value due to __builtin_eh_return pinskia at gcc dot gnu.org 2024-04-25 7:16 ` pinskia at gcc dot gnu.org 2024-04-25 7:26 ` pinskia at gcc dot gnu.org 2024-04-25 7:52 ` pinskia at gcc dot gnu.org 2024-04-25 9:16 ` [Bug target/114843] aarch64: epilogue " pinskia at gcc dot gnu.org 2024-04-25 21:23 ` pinskia at gcc dot gnu.org 2024-04-25 23:51 ` wilco at gcc dot gnu.org 2024-04-25 23:55 ` pinskia at gcc dot gnu.org 2024-04-26 0:01 ` pinskia at gcc dot gnu.org 2024-04-26 0:03 ` wilco at gcc dot gnu.org 2024-04-26 0:31 ` pinskia at gcc dot gnu.org 2024-04-26 1:31 ` pinskia at gcc dot gnu.org 2024-04-26 17:09 ` pinskia at gcc dot gnu.org 2024-04-26 17:48 ` wilco at gcc dot gnu.org 2024-04-26 18:39 ` pinskia at gcc dot gnu.org 2024-04-26 22:22 ` pinskia at gcc dot gnu.org 2024-05-06 0:14 ` pinskia 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-114843-4-soVx0Y3CEm@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: linkBe 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).