public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/96015] [10/11 Regression] gcc-10.1.0 miscompiles Python on hppa Date: Fri, 03 Jul 2020 08:23:43 +0000 [thread overview] Message-ID: <bug-96015-4-9iDYjDFVa1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96015-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96015 --- Comment #29 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- It's again __builtin_unreachable making a mess in the RTL stream: (note 23 11 24 [bb 3] NOTE_INSN_BASIC_BLOCK) (jump_insn:TI 24 23 15 (set (pc) (if_then_else (leu (reg/v:SI 24 %r24 [orig:99 g ] [99]) (const_int 5 [0x5])) (label_ref:SI 81) (pc))) 30 {*pa.md:1413} (int_list:REG_BR_PROB 536870916 (nil)) -> 81) (code_label 15 24 17 4 (nil) [2 uses]) (barrier 17 15 16) (note 16 17 81 [bb 4] NOTE_INSN_BASIC_BLOCK) (code_label 81 16 43 12 (nil) [1 uses]) (note 43 81 25 [bb 5] NOTE_INSN_BASIC_BLOCK) (jump_insn:TI 25 43 26 (parallel [ (set (pc) (mem:SI (plus:SI (mult:SI (reg/v:SI 24 %r24 [orig:99 g ] [99]) (const_int 4 [0x4])) (label_ref 26)) [0 S4 A32])) (clobber (reg:SI 28 %r28)) ]) 198 {casesi32} (expr_list:REG_DEAD (reg/v:SI 24 %r24 [orig:99 g ] [99]) (expr_list:REG_UNUSED (reg:SI 28 %r28) (nil))) -> 26) relax_delay_slots sees that jump_insn 24 jumps to the next active instruction so it proceeds with removing it. Its target label 81 has only one use so it is removed too. At this point delete_related_insns thinks that it can also remove all the instructions after label 81 down to the next label because of the presence of barrier 17: /* If INSN was a label, delete insns following it if now unreachable. */ if (was_code_label && prev && BARRIER_P (prev)) { enum rtx_code code; while (next) {
next prev parent reply other threads:[~2020-07-03 8:23 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 7:29 [Bug target/96015] New: [regression] " slyfox at inbox dot ru 2020-07-01 7:30 ` [Bug target/96015] " slyfox at inbox dot ru 2020-07-01 7:32 ` slyfox at inbox dot ru 2020-07-01 7:38 ` slyfox at inbox dot ru 2020-07-01 8:03 ` [Bug target/96015] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-01 8:11 ` marxin at gcc dot gnu.org 2020-07-01 9:14 ` slyfox at inbox dot ru 2020-07-01 9:15 ` slyfox at inbox dot ru 2020-07-01 13:11 ` marxin at gcc dot gnu.org 2020-07-01 13:12 ` marxin at gcc dot gnu.org 2020-07-01 15:39 ` slyfox at inbox dot ru 2020-07-01 15:40 ` slyfox at inbox dot ru 2020-07-01 15:46 ` slyfox at inbox dot ru 2020-07-01 16:35 ` law at redhat dot com 2020-07-01 17:33 ` law at redhat dot com 2020-07-01 17:57 ` slyfox at inbox dot ru 2020-07-01 19:15 ` slyfox at inbox dot ru 2020-07-02 6:58 ` slyfox at inbox dot ru 2020-07-02 7:58 ` marxin at gcc dot gnu.org 2020-07-02 9:34 ` ebotcazou at gcc dot gnu.org 2020-07-02 17:15 ` slyfox at inbox dot ru 2020-07-02 17:15 ` slyfox at inbox dot ru 2020-07-02 17:16 ` slyfox at inbox dot ru 2020-07-02 20:21 ` slyfox at inbox dot ru 2020-07-02 20:50 ` slyfox at inbox dot ru 2020-07-02 21:35 ` slyfox at inbox dot ru 2020-07-02 22:36 ` slyfox at inbox dot ru 2020-07-02 23:16 ` [Bug rtl-optimization/96015] " ebotcazou at gcc dot gnu.org 2020-07-03 7:19 ` slyfox at inbox dot ru 2020-07-03 7:45 ` marxin at gcc dot gnu.org 2020-07-03 8:23 ` ebotcazou at gcc dot gnu.org [this message] 2020-07-03 9:23 ` ebotcazou at gcc dot gnu.org 2020-07-03 17:24 ` slyfox at inbox dot ru 2020-07-03 19:29 ` ebotcazou at gcc dot gnu.org 2020-07-06 20:31 ` law at redhat dot com 2020-07-07 8:09 ` ebotcazou at gcc dot gnu.org 2020-07-08 17:01 ` law at redhat dot com 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-01-14 9:04 ` rguenth at gcc dot gnu.org 2021-01-14 16:33 ` law at redhat dot com 2021-01-14 19:14 ` mikpelinux at gmail dot com 2021-01-15 16:54 ` ebotcazou at gcc dot gnu.org 2021-02-09 18:56 ` cvs-commit at gcc dot gnu.org 2021-02-09 18:59 ` cvs-commit at gcc dot gnu.org 2021-02-09 19:01 ` ebotcazou at gcc dot gnu.org 2021-02-09 20:21 ` dave.anglin at bell dot net
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-96015-4-9iDYjDFVa1@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).