public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin 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: Wed, 14 Sep 2022 13:41:46 +0000	[thread overview]
Message-ID: <bug-106896-4-Efm5kOXQFv@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 #5 from Martin Liška <marxin at gcc dot gnu.org> ---
> Modelling it
> as a probability would cap one of the two cases to 1 (i.e. same as
> equal counts).

You are correct, Honza should answer here!

  parent reply	other threads:[~2022-09-14 13:41 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 [this message]
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
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-Efm5kOXQFv@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).