public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kristerw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111668] [12/13 Regression] vrp2 (match and simplify) introduces invalid wide signed Boolean values Date: Sun, 08 Oct 2023 21:41:38 +0000 [thread overview] Message-ID: <bug-111668-4-irjHidaLGg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111668-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111668 --- Comment #8 from Krister Walfridsson <kristerw at gcc dot gnu.org> --- I still see negation of a wide signed Boolean in the IR for this function. But now it is forwprop4 that changes _38 = (signed int) _16; _43 = -_38; _66 = (<signed-boolean:32>) _43; to _56 = (<signed-boolean:32>) _16; _66 = -_56;
next prev parent reply other threads:[~2023-10-08 21:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-02 22:14 [Bug tree-optimization/111668] New: vrp2 introduces invalid wide " kristerw at gcc dot gnu.org 2023-10-02 22:28 ` [Bug tree-optimization/111668] vrp2 (match and simplify) introduces invalid wide signed " pinskia at gcc dot gnu.org 2023-10-02 22:30 ` pinskia at gcc dot gnu.org 2023-10-02 22:32 ` [Bug tree-optimization/111668] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-10-03 8:33 ` jakub at gcc dot gnu.org 2023-10-03 8:48 ` jakub at gcc dot gnu.org 2023-10-04 7:29 ` cvs-commit at gcc dot gnu.org 2023-10-04 7:33 ` [Bug tree-optimization/111668] [12/13 " jakub at gcc dot gnu.org 2023-10-04 9:45 ` rguenth at gcc dot gnu.org 2023-10-08 21:41 ` kristerw at gcc dot gnu.org [this message] 2023-11-27 23:22 ` kristerw at gcc dot gnu.org 2024-05-13 11:30 ` rguenth 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-111668-4-irjHidaLGg@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).