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 09:23:42 +0000 [thread overview] Message-ID: <bug-96015-4-VPk2IZ6QpQ@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 #30 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- Not clear what the right fix is... The hot spot in relax_delay_slots: /* If this is a jump insn, see if it now jumps to a jump, jumps to the next insn, or jumps to a label that is not the last of a group of consecutive labels. */ if (is_a <rtx_jump_insn *> (insn) && (condjump_p (insn) || condjump_in_parallel_p (insn)) && !ANY_RETURN_P (target_label = JUMP_LABEL (insn))) { rtx_jump_insn *jump_insn = as_a <rtx_jump_insn *> (insn); target_label = skip_consecutive_labels (follow_jumps (target_label, jump_insn, &crossing)); if (ANY_RETURN_P (target_label)) target_label = find_end_label (target_label); if (target_label && next_active_insn (as_a<rtx_insn *> (target_label)) == next && ! condjump_in_parallel_p (jump_insn) && ! (next && switch_text_sections_between_p (jump_insn, next))) { delete_jump (jump_insn); continue; } IIRC Jeff already dealt with this kind of issues in the past, so maybe he knows what the best way out would be?
next prev parent reply other threads:[~2020-07-03 9: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 2020-07-03 9:23 ` ebotcazou at gcc dot gnu.org [this message] 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-VPk2IZ6QpQ@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).