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 tree-optimization/106896] [13 Regression] ICE in to_sreal_scale, at profile-count.cc:339 since r13-2288-g61c4c989034548f4
Date: Tue, 14 Mar 2023 08:11:02 +0000 [thread overview]
Message-ID: <bug-106896-4-JkrHy4e21W@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>:
https://gcc.gnu.org/g:5159a1f1e91e03d4b82808a0062697318232543f
commit r13-6652-g5159a1f1e91e03d4b82808a0062697318232543f
Author: Jan Hubicka <jh@suse.cz>
Date: Tue Mar 14 09:10:35 2023 +0100
Fix overactive sanity check in profile_count::to_sreal_scale
As discussed in the PR log, profile_count::to_cgraph_frequency was
originally
intended to work across function boundary and has some extra logic and
sanity
check for that. It is used only within single function and with current
API it can not really work well globally, so this patch synchronizes its
implementation with probability_in which does similar job but to determine
relative probability.
gcc/ChangeLog:
2023-03-14 Jan Hubicka <hubicka@ucw.cz>
PR tree-optimization/106896
* profile-count.cc (profile_count::to_sreal_scale): Synchronize
implementatoin with probability_in; avoid some asserts.
next prev parent reply other threads:[~2023-03-14 8:11 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
2023-03-14 8:11 ` cvs-commit at gcc dot gnu.org [this message]
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-JkrHy4e21W@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: link
Be 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).