public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106896] [13 Regression] ICE in to_sreal_scale, at profile-count.cc:339 since r13-2288-g61c4c989034548f4 Date: Mon, 06 Mar 2023 10:34:27 +0000 [thread overview] Message-ID: <bug-106896-4-5F79EzYy5Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106896-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106896 --- Comment #11 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Originally to_sreal_frquency was intended to work both inter-procedurally and intra-procedurally. However in such setup there are side cases that can not be solved without knowing the corresponding entry_bb_counts which are not known to the function. Inspecting existing uses of to_sreal_frequency it is used intra-procedurally only. In that case it makes sense to implement it same way as probability_in which is done by the following patch: diff --git a/gcc/profile-count.cc b/gcc/profile-count.cc index d05fef3fb00..16585045f8e 100644 --- a/gcc/profile-count.cc +++ b/gcc/profile-count.cc @@ -325,6 +325,13 @@ profile_count::to_cgraph_frequency (profile_count entry_bb_count) const sreal profile_count::to_sreal_scale (profile_count in, bool *known) const { + if (*this == zero () + && !(in == zero ())) + { + if (known) + *known = true; + return 0; + } if (!initialized_p () || !in.initialized_p ()) { if (known) @@ -333,32 +340,13 @@ profile_count::to_sreal_scale (profile_count in, bool *known) const } if (known) *known = true; - /* Watch for cases where one count is IPA and other is not. */ - if (in.ipa ().initialized_p ()) - { - gcc_checking_assert (ipa ().initialized_p ()); - /* If current count is inter-procedurally 0 and IN is inter-procedurally - non-zero, return 0. */ - if (in.ipa ().nonzero_p () - && !ipa().nonzero_p ()) - return 0; - } - else - /* We can handle correctly 0 IPA count within locally estimated - profile, but otherwise we are lost and this should not happen. */ - gcc_checking_assert (!ipa ().initialized_p () || !ipa ().nonzero_p ()); - if (*this == zero ()) - return 0; - if (m_val == in.m_val) + if (*this == in) return 1; gcc_checking_assert (compatible_p (in)); - + if (m_val == in.m_val) + return 1; if (!in.m_val) - { - if (!m_val) - return 1; - return m_val * 4; - } + return m_val * 4; return (sreal)m_val / (sreal)in.m_val; }
next prev parent reply other threads:[~2023-03-06 10:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-09 14:12 [Bug tree-optimization/106896] New: [13 Regression] ICE in to_sreal_scale, at profile-count.cc:339 asolokha at gmx dot com 2022-09-12 7:43 ` [Bug tree-optimization/106896] " rguenth at gcc dot gnu.org 2022-09-12 11:21 ` rsandifo at gcc dot gnu.org 2022-09-12 14:13 ` [Bug tree-optimization/106896] [13 Regression] ICE in to_sreal_scale, at profile-count.cc:339 since r13-2288-g61c4c989034548f4 marxin at gcc dot gnu.org 2022-09-12 14:26 ` marxin at gcc dot gnu.org 2022-09-14 12:43 ` rsandifo at gcc dot gnu.org 2022-09-14 13:41 ` marxin at gcc dot gnu.org 2022-10-18 8:47 ` rguenth at gcc dot gnu.org 2022-10-26 9:07 ` rsandifo at gcc dot gnu.org 2022-12-19 23:25 ` pinskia at gcc dot gnu.org 2023-02-06 12:01 ` jakub at gcc dot gnu.org 2023-03-03 16:18 ` hubicka at gcc dot gnu.org 2023-03-06 10:34 ` hubicka at gcc dot gnu.org [this message] 2023-03-14 8:11 ` cvs-commit at gcc dot gnu.org 2023-03-14 8:12 ` hubicka 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-106896-4-5F79EzYy5Z@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).