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/112738] [14 Regression] forwprop4 introduces invalid wide signed Boolean values Date: Mon, 27 Nov 2023 23:26:09 +0000 [thread overview] Message-ID: <bug-112738-4-zuYqKVmobP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112738-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112738 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Summary|forwprop4 introduces |[14 Regression] forwprop4 |invalid wide signed Boolean |introduces invalid wide |values |signed Boolean values Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Target Milestone|--- |14.0 Last reconfirmed| |2023-11-27 Keywords| |wrong-code Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Mine. ``` /* (nop_outer_cast)-(inner_cast)var -> -(outer_cast)(var) if var is smaller in precision. This is always safe for both doing the negative in signed or unsigned as the value for undefined will not show up. */ (simplify (convert (negate:s@1 (convert:s @0))) (if (INTEGRAL_TYPE_P (type) && tree_nop_conversion_p (type, TREE_TYPE (@1)) && TYPE_PRECISION (type) > TYPE_PRECISION (TREE_TYPE (@0))) (negate (convert @0)))) ``` This needs a check for !BOOLEAN_TYPE here I think. boolean is the special case ...
next prev parent reply other threads:[~2023-11-27 23:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 23:21 [Bug tree-optimization/112738] New: " kristerw at gcc dot gnu.org 2023-11-27 23:26 ` pinskia at gcc dot gnu.org [this message] 2023-11-27 23:34 ` [Bug tree-optimization/112738] [14 Regression] " pinskia at gcc dot gnu.org 2023-11-28 17:52 ` cvs-commit at gcc dot gnu.org 2023-11-28 17:52 ` 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-112738-4-zuYqKVmobP@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).