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 target/103932] x86: strange unoptimized code generated (multiple negations of _mm_testz_si128 result) Date: Thu, 06 Jan 2022 21:23:20 +0000 [thread overview] Message-ID: <bug-103932-4-PpOQVkv8kc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103932-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103932 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Last reconfirmed| |2022-01-06 Ever confirmed|0 |1 Severity|normal |enhancement Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The gimple level is decent: _7 = __builtin_ia32_ptestz128 (_4, _4); _1 = _7 == 0; bit_5 = (const u64) _1; Though _7 is already 0 or 1. The problem is the target does not say the range of __builtin_ia32_ptestz128 is 0 or 1.
next prev parent reply other threads:[~2022-01-06 21:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-06 19:11 [Bug c++/103932] New: " nekotekina at gmail dot com 2022-01-06 21:23 ` pinskia at gcc dot gnu.org [this message] 2022-01-06 21:25 ` [Bug target/103932] " 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-103932-4-PpOQVkv8kc@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).