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 rtl-optimization/110307] ICE in move_insn, at haifa-sched.cc:5473 when building Ruby on alpha with -fPIC -O2 (or -fpeephole2 -fschedule-insns2) Date: Tue, 20 Jun 2023 21:45:26 +0000 [thread overview] Message-ID: <bug-110307-4-jBAN9zsLIW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110307-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110307 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Alexander Monakov from comment #6) > Note the REG_EH_REGION. This is relevant because can_nonlocal_goto checks > it, so for insn 25 we knew it wouldn't return to the setjmp receiver. > Applying the peephole dropped the note. This should fix it but there might be other REG notes that need to be copied still: apinski@xeond:~/src/upstream-gcc/gcc/gcc$ git diff recog.cc diff --git a/gcc/recog.cc b/gcc/recog.cc index 37432087812..4bad4a59057 100644 --- a/gcc/recog.cc +++ b/gcc/recog.cc @@ -3921,6 +3921,7 @@ peep2_attempt (basic_block bb, rtx_insn *insn, int match_len, rtx_insn *attempt) { case REG_NORETURN: case REG_SETJMP: + case REG_EH_REGION: case REG_TM: case REG_CALL_NOCF_CHECK: add_reg_note (new_insn, REG_NOTE_KIND (note),
next prev parent reply other threads:[~2023-06-20 21:45 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 7:08 [Bug rtl-optimization/110307] New: ICE in move_insn, at haifa-sched.cc:5473 on alpha with -fPIC -fpeephole2 -fschedule-insns2 matoro_gcc_bugzilla at matoro dot tk 2023-06-19 11:13 ` [Bug rtl-optimization/110307] " amonakov at gcc dot gnu.org 2023-06-19 20:28 ` [Bug rtl-optimization/110307] ICE in move_insn, at haifa-sched.cc:5473 when building Ruby on alpha with -fPIC -O2 (or -fpeephole2 -fschedule-insns2) matoro_gcc_bugzilla at matoro dot tk 2023-06-19 22:07 ` amonakov at gcc dot gnu.org 2023-06-19 23:02 ` matoro_gcc_bugzilla at matoro dot tk 2023-06-20 9:03 ` amonakov at gcc dot gnu.org 2023-06-20 16:42 ` amonakov at gcc dot gnu.org 2023-06-20 21:45 ` pinskia at gcc dot gnu.org [this message] 2023-06-21 11:08 ` amonakov at gcc dot gnu.org 2023-06-22 14:53 ` matoro_gcc_bugzilla at matoro dot tk 2023-06-22 15:55 ` amonakov at gcc dot gnu.org 2023-06-22 16:17 ` matoro_gcc_bugzilla at matoro dot tk 2023-06-25 16:39 ` matoro_gcc_bugzilla at matoro dot tk 2023-06-25 16:46 ` amonakov at gcc dot gnu.org 2023-11-10 21:37 ` sjames at gcc dot gnu.org 2023-11-11 9:01 ` amonakov 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-110307-4-jBAN9zsLIW@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).