public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov 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 16:42:30 +0000 [thread overview] Message-ID: <bug-110307-4-ArZ3mi0Ndp@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 #6 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Cross-compiler needs HAVE_AS_EXPLICIT_RELOCS=1. With checking enabled, we get: t.c:8:1: error: flow control insn inside a basic block (call_insn 97 96 98 4 (parallel [ (set (reg:DI 0 $0) (call (mem:DI (reg:DI 27 $27) [0 S8 A64]) (const_int 0 [0]))) (set (reg:DI 29 $29) (unspec:DI [ (reg:DI 29 $29) (const_int 6 [0x6]) ] UNSPEC_LDGP1)) (use (symbol_ref:DI ("__tls_get_addr") [flags 0x41] <function_decl 0x7f642d9ec400 __tls_get_addr>)) (use (unspec [ (const_int 1 [0x1]) ] UNSPEC_TLSGD_CALL)) (clobber (reg:DI 26 $26)) ]) "t.c":6:22 -1 (nil) (expr_list (use (reg:DI 16 $16)) (nil))) during RTL pass: peephole2 dump file: t.c.313r.peephole2 t.c:8:1: internal compiler error: in rtl_verify_bb_insns, at cfgrtl.cc:2797 Insn 96 appears via: Splitting with gen_peephole2_8 (alpha.md:5972) scanning new insn with uid = 96. scanning new insn with uid = 97. scanning new insn with uid = 98. deleting insn with uid = 25. Insn 25 was: (call_insn/u 25 39 26 4 (parallel [ (set (reg:DI 0 $0) (call (mem:DI (symbol_ref:DI ("__tls_get_addr") [flags 0x41] <function_decl 0x7f642d9ec400 __tls_get_addr>) [0 S8 A64]) (const_int 0 [0]))) (unspec [ (const_int 1 [0x1]) ] UNSPEC_TLSGD_CALL) (use (reg:DI 29 $29)) (clobber (reg:DI 26 $26)) ]) "t.c":6:22 346 {call_value_osf_tlsgd} (expr_list:REG_DEAD (reg:DI 16 $16) (expr_list:REG_EH_REGION (const_int -2147483648 [0xffffffff80000000]) (nil))) (expr_list (use (reg:DI 16 $16)) (nil))) 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.
next prev parent reply other threads:[~2023-06-20 16:42 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 [this message] 2023-06-20 21:45 ` pinskia at gcc dot gnu.org 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-ArZ3mi0Ndp@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).