public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108997] GCC prediction on bool comparisons seems wrong
Date: Fri, 03 Mar 2023 00:10:38 +0000 [thread overview]
Message-ID: <bug-108997-4-Dg2RszY6Hw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108997-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108997
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Nikita Kniazev from comment #3)
> For cond == 789
> if (cond_2(D) == 789)
> goto <bb 3>; [20.24%]
> else
> goto <bb 4>; [79.76%]
>
> For cond != 789
> if (cond_2(D) != 789)
> goto <bb 3>; [48.88%]
> else
> goto <bb 4>; [51.12%]
an intergal type equaling a specific # is handled this way on purpose. Bool
should be handled differently because it only has two values, 0/1.
Anyways != is not handled specially except for the zero value case ...
next prev parent reply other threads:[~2023-03-03 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 22:51 [Bug tree-optimization/108997] New: " pinskia at gcc dot gnu.org
2023-03-02 23:26 ` [Bug tree-optimization/108997] " nok.raven at gmail dot com
2023-03-02 23:35 ` pinskia at gcc dot gnu.org
2023-03-03 0:05 ` nok.raven at gmail dot com
2023-03-03 0:10 ` pinskia at gcc dot gnu.org [this message]
2023-03-03 8:43 ` rguenth at gcc dot gnu.org
2023-03-07 14:49 ` 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-108997-4-Dg2RszY6Hw@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).