public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/100254] [11/12 Regression] -fcompare-debug failure (length) with -O2 -fno-guess-branch-probability -fipa-pta -fnon-call-exceptions Date: Tue, 27 Apr 2021 13:32:50 +0000 [thread overview] Message-ID: <bug-100254-4-vmeFDJUW6w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100254 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7f8eea0b16494554d623113c8138879b3f31d67a commit r11-8299-g7f8eea0b16494554d623113c8138879b3f31d67a Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 27 15:26:24 2021 +0200 cfgcleanup: Fix -fcompare-debug issue in outgoing_edges_match [PR100254] The following testcase fails with -fcompare-debug. The problem is that outgoing_edges_match behaves differently between -g0 and -g, if some load/store with REG_EH_REGION is followed by DEBUG_INSNs, the REG_EH_REGION check is not done, while when there are no DEBUG_INSNs, it is done. We already compute last1 and last2 as BB_END (bb{1,2}) with skipped debug insns and notes, so this patch just uses those. 2021-04-27 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/100254 * cfgcleanup.c (outgoing_edges_match): Check REG_EH_REGION on last1 and last2 insns rather than BB_END (bb1) and BB_END (bb2) insns. * g++.dg/opt/pr100254.C: New test. (cherry picked from commit e600df51a15b2ec7a72731921a2464ffe59cf5ab)
next prev parent reply other threads:[~2021-04-27 13:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-25 19:21 [Bug debug/100254] New: " zsojka at seznam dot cz 2021-04-26 7:30 ` [Bug debug/100254] " rguenth at gcc dot gnu.org 2021-04-26 8:28 ` jakub at gcc dot gnu.org 2021-04-26 9:41 ` jakub at gcc dot gnu.org 2021-04-26 10:42 ` [Bug rtl-optimization/100254] " jakub at gcc dot gnu.org 2021-04-27 13:27 ` cvs-commit at gcc dot gnu.org 2021-04-27 13:32 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-27 13:34 ` jakub at gcc dot gnu.org 2021-05-04 12:08 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:21 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:26 ` cvs-commit 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-100254-4-vmeFDJUW6w@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).