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/101301] Improving sparse switch statement
Date: Thu, 12 Aug 2021 10:31:40 +0000	[thread overview]
Message-ID: <bug-101301-4-CxaGRRJfA8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101301-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101301

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
   Last reconfirmed|                            |2021-08-12
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1

--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
> Ha :-)  Too bad we can only warn "invalid sum of incoming frequencies", it
> still
> happens too often (read: at all) to actually error on it...  that would
> perhaps
> grab people's attention :-)

I can confirm switch lowering is not updating BB counts and I see some other
issues related to edge probabilities. I have a partial fix, but I'm going to
return to it once stage1 is gone.

  parent reply	other threads:[~2021-08-12 10:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 15:32 [Bug tree-optimization/101301] New: " tkoenig at gcc dot gnu.org
2021-07-03 10:41 ` [Bug tree-optimization/101301] " tkoenig at gcc dot gnu.org
2021-07-03 18:42 ` tkoenig at gcc dot gnu.org
2021-07-03 19:34 ` segher at gcc dot gnu.org
2021-07-03 21:57 ` tkoenig at gcc dot gnu.org
2021-07-04 17:37 ` segher at gcc dot gnu.org
2021-07-05  5:33 ` tkoenig at gcc dot gnu.org
2021-07-05 17:33 ` segher at gcc dot gnu.org
2021-07-06 13:39 ` tkoenig at gcc dot gnu.org
2021-07-06 16:35 ` segher at gcc dot gnu.org
2021-08-12 10:31 ` marxin at gcc dot gnu.org [this message]
2022-11-30 13:04 ` cvs-commit at gcc dot gnu.org
2023-04-03  9:04 ` marxin 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-101301-4-CxaGRRJfA8@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).