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 rtl-optimization/94618] [8/9/10 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions since r8-565-g7581ce9a1ad6df9c Date: Fri, 17 Apr 2020 07:54:43 +0000 [thread overview] Message-ID: <bug-94618-4-Jddtu2nFc7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94618-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94618 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Though, a slight advantage of the patch as is is that it will do any insn walk only if two conditions are met, BB_END is a DEBUG_INSN and insn is followed by a DEBUG_INSN. My thoughs were that there could be a large bb with hundreds of DEBUG_INSNs at the end and if we e.g. started deleting insn from the start, even if they aren't really followed by any DEBUG_INSNs, we'd still walk all of them each time.
next prev parent reply other threads:[~2020-04-17 7:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-16 13:04 [Bug debug/94618] New: [10 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions zsojka at seznam dot cz 2020-04-16 14:00 ` [Bug debug/94618] [8/9/10 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions since r8-565-g7581ce9a1ad6df9c marxin at gcc dot gnu.org 2020-04-16 14:18 ` jakub at gcc dot gnu.org 2020-04-16 14:26 ` [Bug rtl-optimization/94618] " rguenth at gcc dot gnu.org 2020-04-16 14:44 ` jakub at gcc dot gnu.org 2020-04-16 15:37 ` jakub at gcc dot gnu.org 2020-04-17 7:35 ` rguenth at gcc dot gnu.org 2020-04-17 7:51 ` jakub at gcc dot gnu.org 2020-04-17 7:54 ` jakub at gcc dot gnu.org [this message] 2020-04-17 8:34 ` cvs-commit at gcc dot gnu.org 2020-04-17 8:35 ` [Bug rtl-optimization/94618] [8/9 " jakub at gcc dot gnu.org 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:34 ` jakub at gcc dot gnu.org 2022-05-27 13:15 ` rguenth 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-94618-4-Jddtu2nFc7@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).