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/110487] [12/13/14 Regression] invalid wide Boolean value Date: Tue, 04 Jul 2023 17:20:12 +0000 [thread overview] Message-ID: <bug-110487-4-31siGEcHYq@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 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:71b68cc559b5d30d07e6b507df7cc6d008f56aad commit r14-2299-g71b68cc559b5d30d07e6b507df7cc6d008f56aad Author: Andrew Pinski <apinski@marvell.com> Date: Fri Jun 30 19:22:48 2023 -0700 PR 110487: `(a !=/== CST1 ? CST2 : CST3)` pattern for type safety The problem here is we might produce some values out of the type's min/max (and/or valid values, e.g. signed booleans). The fix is to use an integer type which has the same precision and signedness as the original type. Note two_value_replacement in phiopt had the same issue in previous versions; though I don't know if a problem will show up there. OK? Bootstrapped and tested on x86_64-linux-gnu. gcc/ChangeLog: PR tree-optimization/110487 * match.pd (a !=/== CST1 ? CST2 : CST3): Always build a nonstandard integer and use that.
next prev parent reply other threads:[~2023-07-04 17:20 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 ` [Bug tree-optimization/110487] " pinskia at gcc dot gnu.org 2023-06-29 19:13 ` 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 [this message] 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-31siGEcHYq@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: linkBe 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).