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/111149] bool0 != bool1 should be expanded as bool0 ^ bool1
Date: Wed, 30 Aug 2023 05:13:18 +0000	[thread overview]
Message-ID: <bug-111149-4-zvl6VAHWuf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111149-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111149

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> So g++.dg/vect/simd-bool-comparison-1.cc fails with the canonicalization ...
> Looking into how to fix that too.

The difference is:
  _3 = _1 ^ c.0_2;
  cstore_10 = _3 ? 0.0 : 1.0e+0;


vs:
  _3 = _1 != c.0_2;
  cstore_10 = _3 ? 0.0 : 1.0e+0;


Original:
/app/example.cpp:12:17: note:   === vect_determine_precisions ===
/app/example.cpp:12:17: note:   using boolean precision 8 for _3 = _1 != c.0_2;

New:
t.cc:14:17: note:   === vect_determine_precisions ===
t.cc:14:17: note:   using normal nonmask vectors for _3 = _1 ^ c.0_2;

  parent reply	other threads:[~2023-08-30  5:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  2:09 [Bug tree-optimization/111149] New: bool0 != bool1 should be convert into " pinskia at gcc dot gnu.org
2023-08-25  2:09 ` [Bug tree-optimization/111149] " pinskia at gcc dot gnu.org
2023-08-25  2:21 ` [Bug middle-end/111149] bool0 != bool1 should be expanded as " pinskia at gcc dot gnu.org
2023-08-29  4:24 ` [Bug tree-optimization/111149] " pinskia at gcc dot gnu.org
2023-08-29 17:14 ` pinskia at gcc dot gnu.org
2023-08-29 17:23 ` pinskia at gcc dot gnu.org
2023-08-30  0:15 ` pinskia at gcc dot gnu.org
2023-08-30  5:07 ` pinskia at gcc dot gnu.org
2023-08-30  5:13 ` pinskia at gcc dot gnu.org [this message]
2023-08-30  6:11 ` 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-111149-4-zvl6VAHWuf@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).