public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100738] Gimple failed to simplify ((v4si) ~a) < 0 ? c : d to ((v4si)a) >= 0 ? c : d
Date: Wed, 26 May 2021 10:48:19 +0000 [thread overview]
Message-ID: <bug-100738-4-jcRq9Bzf5c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100738
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Richard Biener from comment #2)
> Confirmed. Watch out for (v4sf)~a though. Note there's
Not sure for (v4sf)~a if we honor NANs, (v4sf)~a < 0 could be different from
(v4sf)a >= 0;
next prev parent reply other threads:[~2021-05-26 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 8:21 [Bug middle-end/100738] New: " crazylht at gmail dot com
2021-05-24 8:59 ` [Bug middle-end/100738] " pinskia at gcc dot gnu.org
2021-05-25 7:39 ` rguenth at gcc dot gnu.org
2021-05-26 10:48 ` crazylht at gmail dot com [this message]
2021-05-27 6:22 ` crazylht at gmail dot com
2021-12-08 6:13 ` cvs-commit at gcc dot gnu.org
2021-12-08 6:15 ` crazylht at gmail dot com
2021-12-17 5:56 ` cvs-commit 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-100738-4-jcRq9Bzf5c@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).