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 target/98648] Failure to optimize out no-op vector operation using andnot Date: Thu, 14 Jan 2021 10:58:12 +0000 [thread overview] Message-ID: <bug-98648-4-bRojqe31Xi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98648-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98648 Hongtao.liu <crazylht at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crazylht at gmail dot com --- Comment #2 from Hongtao.liu <crazylht at gmail dot com> --- It looks like not an ABI issue, but gcc didn't simplify for vector all one bits for floating point. .277r.combine Trying 6 -> 7: 6: r85:V4SF=const_vector 7: r84:V4SF=~r85:V4SF&r87:V4SF REG_DEAD r87:V4SF REG_DEAD r85:V4SF Failed to match this instruction: (set (reg:V4SF 84) (and:V4SF (reg:V4SF 87) (const_vector:V4SF [ (const_double:SF -QNaN [-QNaN]) repeated x4 ]))) When NAN is all ones(which is situation here), it should be simplified to (set (reg:V4SF 84) (reg: V4SF 87))
next prev parent reply other threads:[~2021-01-14 10:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-13 1:02 [Bug target/98648] New: " gabravier at gmail dot com 2021-01-13 1:09 ` [Bug target/98648] " pinskia at gcc dot gnu.org 2021-01-14 10:58 ` crazylht at gmail dot com [this message] 2021-01-14 11:16 ` jakub at gcc dot gnu.org 2021-01-14 15:32 ` gabravier at gmail dot com 2021-12-15 1:16 ` pinskia at gcc dot gnu.org 2021-12-15 1:16 ` pinskia at gcc dot gnu.org 2021-12-20 2:33 ` crazylht at gmail dot com 2021-12-20 2:35 ` 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-98648-4-bRojqe31Xi@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).