public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95924] Failure to optimize some bit magic to one of the operands Date: Sat, 27 Jun 2020 12:27:12 +0000 [thread overview] Message-ID: <bug-95924-4-LdHQTad24X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95924-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95924 --- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> --- * If I replace ~a with !a, we manage to do everything with type bool. With ~a, we don't, we stick to int. * We don't handle a?b:false the same as a&&b. * Even for (a | !b) && (!(!a & b) && a) we don't completely simplify, because that would be replacing too many && with & (I think). If I manually replace one && with &, gcc manages.
next prev parent reply other threads:[~2020-06-27 12:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-27 1:06 [Bug tree-optimization/95924] New: " gabravier at gmail dot com 2020-06-27 12:27 ` glisse at gcc dot gnu.org [this message] 2021-07-25 4:53 ` [Bug tree-optimization/95924] " pinskia at gcc dot gnu.org 2023-08-22 5:29 ` 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-95924-4-LdHQTad24X@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).