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 tree-optimization/103462] GCC failed to reduce bit clear in loop. Date: Mon, 29 Nov 2021 05:26:22 +0000 [thread overview] Message-ID: <bug-103462-4-Av6maVTMBD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103462-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103462 --- Comment #2 from Hongtao.liu <crazylht at gmail dot com> --- bit clear and induction variable could be simplified to `& CONSTANT`
next prev parent reply other threads:[~2021-11-29 5:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 5:15 [Bug tree-optimization/103462] New: vectorizer failed to reduce bit_clear " crazylht at gmail dot com 2021-11-29 5:19 ` [Bug tree-optimization/103462] GCC failed to reduce bit clear " crazylht at gmail dot com 2021-11-29 5:26 ` crazylht at gmail dot com [this message] 2021-11-29 5:28 ` pinskia at gcc dot gnu.org 2021-11-29 5:35 ` pinskia at gcc dot gnu.org 2021-11-29 8:29 ` rguenth at gcc dot gnu.org 2021-12-15 4:43 ` crazylht at gmail dot com 2021-12-15 4:50 ` crazylht at gmail dot com 2022-05-18 7:47 ` cvs-commit at gcc dot gnu.org 2022-05-18 8:06 ` crazylht at gmail dot com
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-103462-4-Av6maVTMBD@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).