public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/106751] internal compiler error: in purge_dead_edges with inline-asm goto Date: Tue, 13 Sep 2022 15:50:54 +0000 [thread overview] Message-ID: <bug-106751-4-EUItyuHAGt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106751 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> --- For me (powerpc64-linux) it fails with === 106751.c:10:1: error: flow control insn inside a basic block (jump_insn 6 3 13 2 (parallel [ (asm_operands/v ("") ("") 0 [] [] [ (label_ref:DI 9) ] 106751.c:5) (clobber (reg:SI 98 ca)) ]) "106751.c":5:3 -1 (expr_list:REG_UNUSED (reg:SI 98 ca) (nil)) -> 9) during RTL pass: loop2_invariant === That pass did === Set in insn 13 is invariant (0), cost 4, depends on Decided to move invariant 0 -- gain 4 Invariant 0 moved without introducing a new temporary register changing bb of uid 13 from 3 to 2 === It moved the insn after a jump_insn, not a good idea: === (jump_insn 6 3 13 2 (parallel [ (asm_operands/v ("") ("") 0 [] [] [ (label_ref:DI 9) ] 106751.c:5) (clobber (reg:SI 98 ca)) ]) "106751.c":5:3 -1 (expr_list:REG_UNUSED (reg:SI 98 ca) (nil)) -> 9) (insn 13 6 9 2 (set (reg:SI 119) (const_int 0 [0])) "106751.c":9:28 562 {*movsi_internal1} (nil)) ;; succ: 3 [always] count:10631108 (estimated locally) === Maybe it does not see this is an unconditional jump insn?
next prev parent reply other threads:[~2022-09-13 15:50 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-26 10:09 [Bug c/106751] New: internal compiler error: in purge_dead_edges, at cfgrtl.cc:3347 christophe.leroy at csgroup dot eu 2022-08-26 10:10 ` [Bug c/106751] " christophe.leroy at csgroup dot eu 2022-08-26 12:20 ` [Bug target/106751] " christophe.leroy at csgroup dot eu 2022-08-26 12:38 ` marxin at gcc dot gnu.org 2022-08-26 18:07 ` [Bug middle-end/106751] internal compiler error: in purge_dead_edges with inline-asm goto pinskia at gcc dot gnu.org 2022-08-26 18:08 ` pinskia at gcc dot gnu.org 2022-08-26 18:14 ` [Bug rtl-optimization/106751] " pinskia at gcc dot gnu.org 2022-08-26 18:21 ` pinskia at gcc dot gnu.org 2022-09-13 15:50 ` segher at gcc dot gnu.org [this message] 2022-12-15 13:10 ` [Bug rtl-optimization/106751] [10/11/12/13 Regression] " jakub at gcc dot gnu.org 2022-12-15 15:51 ` jakub at gcc dot gnu.org 2022-12-15 16:53 ` jakub at gcc dot gnu.org 2022-12-15 18:05 ` rguenth at gcc dot gnu.org 2022-12-16 9:20 ` cvs-commit at gcc dot gnu.org 2022-12-16 9:23 ` [Bug rtl-optimization/106751] [10/11/12 " jakub at gcc dot gnu.org 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:56 ` [Bug rtl-optimization/106751] [10/11 " jakub at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 9:26 ` [Bug rtl-optimization/106751] [10 " jakub at gcc dot gnu.org 2023-05-03 15:20 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:19 ` jakub 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-106751-4-EUItyuHAGt@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).