public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.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 02:42:50 +0000 [thread overview] Message-ID: <bug-113109-4-shOrQ85bx4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113109-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113109 --- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- It's __builtin_eh_return( that's miscompiled, such that the "handler" isn't installed and the calling function will return to its caller instead of the handler. For the example below: void f(__UINTPTR_TYPE__ p1, void *p2) { __builtin_eh_return(p1, p2); } ...there's a tell-tale diff between 6673 and 6674 in generated assembly code at -O2: @@ -23,7 +23,6 @@ _f: move.d $r13,[$sp] .LCFI5: move.d $r10,$r9 - move.d $r11,[$sp+16] move.d [$sp+],$r13 move.d [$sp+],$r12 move.d [$sp+],$r11 cris.h defines EH_RETURN_HANDLER_RTX (as a call to cris_return_addr_rtx yielding) gen_rtx_MEM (Pmode, plus_constant (Pmode, virtual_incoming_args_rtx, -4)). I'm "guessing" that the problem with the patch, is that anything any port stores through a pointer based on virtual_incoming_args_rtx before returning, is now eliminated.
next prev parent reply other threads:[~2023-12-23 2:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-22 2:12 [Bug middle-end/113109] New: " hp at gcc dot gnu.org 2023-12-22 2:22 ` [Bug middle-end/113109] " pinskia at gcc dot gnu.org 2023-12-22 2:24 ` pinskia at gcc dot gnu.org 2023-12-22 2:51 ` hp at gcc dot gnu.org 2023-12-23 2:42 ` hp at gcc dot gnu.org [this message] 2023-12-23 6:20 ` pinskia at gcc dot gnu.org 2023-12-23 17:19 ` hp at gcc dot gnu.org 2023-12-23 17:25 ` pinskia at gcc dot gnu.org 2023-12-24 0:19 ` guojiufu at gcc dot gnu.org 2023-12-24 0:34 ` guojiufu at gcc dot gnu.org 2023-12-24 0:41 ` cvs-commit at gcc dot gnu.org 2023-12-24 0:58 ` hp at gcc dot gnu.org 2023-12-24 1:01 ` hp at gcc dot gnu.org 2023-12-24 1:01 ` hp at gcc dot gnu.org 2023-12-24 1:16 ` guojiufu at gcc dot gnu.org 2023-12-24 9:13 ` hp 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-113109-4-shOrQ85bx4@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).