public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103793] [12 Regression] ICE: in to_reg_br_prob_base, at profile-count.h:277 with -O3 -fno-guess-branch-probability since r12-6086-gcd5ae148c47c6dee Date: Wed, 22 Dec 2021 01:59:03 +0000 [thread overview] Message-ID: <bug-103793-4-h0LnfMIPJs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103793-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103793 luoxhu at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |luoxhu at gcc dot gnu.org --- Comment #2 from luoxhu at gcc dot gnu.org --- Confirmed. -fno-guess-branch-probability requires the profile_count be initialized, so add guard like this? + if (true_edge->probability.initialized_p ()) + { + edge exit_to_latch1 = single_pred_edge (loop1->latch); + exit_to_latch1->probability + = exit_to_latch1->probability.apply_scale ( + true_edge->probability.to_reg_br_prob_base (), + REG_BR_PROB_BASE); + single_exit (loop1)->probability + = exit_to_latch1->probability.invert (); + }
next prev parent reply other threads:[~2021-12-22 1:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 16:36 [Bug tree-optimization/103793] New: [12 Regression] ICE: in to_reg_br_prob_base, at profile-count.h:277 with -O3 -fno-guess-branch-probability zsojka at seznam dot cz 2021-12-21 16:48 ` [Bug tree-optimization/103793] [12 Regression] ICE: in to_reg_br_prob_base, at profile-count.h:277 with -O3 -fno-guess-branch-probability since r12-6086-gcd5ae148c47c6dee marxin at gcc dot gnu.org 2021-12-22 1:59 ` luoxhu at gcc dot gnu.org [this message] 2021-12-29 1:11 ` cvs-commit at gcc dot gnu.org 2021-12-29 1:16 ` luoxhu 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-103793-4-h0LnfMIPJs@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).