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/110487] invalid wide Boolean value
Date: Thu, 29 Jun 2023 19:09:48 +0000 [thread overview]
Message-ID: <bug-110487-4-ZNCvC73xIU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110487-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Keywords| |wrong-code
Last reconfirmed| |2023-06-29
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Applying pattern match.pd:4705, gimple-match-10.cc:15878
gimple_simplified to _38 = (<signed-boolean:32>) _16;
_66 = -_38;
Global Exported: _66 = [irange] <signed-boolean:32> [-1, 0]
Folded into: _66 = -_38;
/* a ? -1 : 0 -> -a. No need to check the TYPE_PRECISION not being 1
here as the powerof2cst case above will handle that case correctly. */
(if (INTEGRAL_TYPE_P (type) && integer_all_onesp (@1))
(negate (convert (convert:boolean_type_node @0))))))
I guess is mine ....
next prev parent reply other threads:[~2023-06-29 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 19:02 [Bug tree-optimization/110487] New: " kristerw at gcc dot gnu.org
2023-06-29 19:09 ` pinskia at gcc dot gnu.org [this message]
2023-06-29 19:13 ` [Bug tree-optimization/110487] " pinskia at gcc dot gnu.org
2023-06-29 19:14 ` [Bug tree-optimization/110487] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-06-29 23:10 ` pinskia at gcc dot gnu.org
2023-06-30 7:01 ` rguenth at gcc dot gnu.org
2023-06-30 12:50 ` pinskia at gcc dot gnu.org
2023-07-01 0:48 ` pinskia at gcc dot gnu.org
2023-07-01 0:49 ` pinskia at gcc dot gnu.org
2023-07-01 1:01 ` pinskia at gcc dot gnu.org
2023-07-01 1:03 ` pinskia at gcc dot gnu.org
2023-07-01 2:48 ` pinskia at gcc dot gnu.org
2023-07-01 2:49 ` pinskia at gcc dot gnu.org
2023-07-04 17:20 ` cvs-commit at gcc dot gnu.org
2023-07-04 17:20 ` cvs-commit at gcc dot gnu.org
2023-07-04 17:22 ` pinskia 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-110487-4-ZNCvC73xIU@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).