public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/98331] [8/9/10/11 Regression] ICE in haifa_luid_for_non_insn, at haifa-sched.c:7845 since r8-5479-g67a8d7199fe4e474 Date: Thu, 28 Jan 2021 13:37:19 +0000 [thread overview] Message-ID: <bug-98331-4-nVqqKZyxcg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98331-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98331 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 50073 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50073&action=edit gcc11-pr98331.patch Untested fix. If there are debug insns in between a flow control insn and barrier after it and that barrier is later followed by some normal insn other than label (i.e. dead insn), without -g we'd split after the barrier, which puts the barrier in between bbs. But with -g, the code would incorrectly split before the first debug insn following the control flow, which results in a barrier inside of a bb rather than in between and also different behavior from -g0. If there are debug insns after the barrier, we should obviously split before the first of those debug insns (i.e. after the barrier) like we'd do with -g0.
next prev parent reply other threads:[~2021-01-28 13:37 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 18:37 [Bug c++/98331] New: [9/10/11 Regression] ICE in haifa_luid_for_non_insn, at haifa-sched.c:7845 gscfq@t-online.de 2020-12-17 11:16 ` [Bug c++/98331] [9/10/11 Regression] ICE in haifa_luid_for_non_insn, at haifa-sched.c:7845 since r8-5479-g67a8d7199fe4e474 marxin at gcc dot gnu.org 2021-01-04 15:33 ` rguenth at gcc dot gnu.org 2021-01-14 11:08 ` rguenth at gcc dot gnu.org 2021-01-28 10:56 ` jakub at gcc dot gnu.org 2021-01-28 11:15 ` [Bug c++/98331] [8/9/10/11 " jakub at gcc dot gnu.org 2021-01-28 13:37 ` jakub at gcc dot gnu.org [this message] 2021-01-29 9:31 ` [Bug debug/98331] " cvs-commit at gcc dot gnu.org 2021-01-29 9:32 ` [Bug debug/98331] [8/9/10 " jakub at gcc dot gnu.org 2021-01-29 19:20 ` cvs-commit at gcc dot gnu.org 2021-01-29 19:24 ` [Bug debug/98331] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:08 ` 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-98331-4-nVqqKZyxcg@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).