public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107671] i386: Missed optimization: use of bt in bit test pattern (using -O2 -mtune=core2) Date: Mon, 14 Nov 2022 04:00:39 +0000 [thread overview] Message-ID: <bug-107671-4-0l9joILO8X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107671-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107671 --- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> --- Expected generated code would be: --- bt32_setb*: ... shrl $5, %edx movl (%eax,%edx,4), %edx xorl %eax, %eax btl %ecx, %edx setb %al ... --- bt32_setae*: ... shrl $5, %edx movl (%eax,%edx,4), %edx xorl %eax, %eax btl %ecx, %edx setae %al ... --- bt32v_setb*: ... xorl %eax, %eax btl %esi, %edi setb %al ... --- bt32v_setae*: ... xorl %eax, %eax btl %esi, %edi setae %al ... --- bt64_setb*: ... shrq $6, %rax movq (%rdi,%rax,8), %rcx xorl %eax, %eax btq %rsi, %rcx setb %al ... --- bt64_setae*: ... shrq $6, %rax movq (%rdi,%rax,8), %rcx xorl %eax, %eax btq %rsi, %rcx setae %al ... --- bt64v_setb*: ... xorl %eax, %eax btq %rsi, %rdi setb %al ... --- bt64v_setae*: ... xorl %eax, %eax btq %rsi, %rdi setae %al ...
next prev parent reply other threads:[~2022-11-14 4:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-14 3:38 [Bug target/107671] New: i386: Missed optimization: use of bt in bit test pattern when LHS is an array index ibuclaw at gdcproject dot org 2022-11-14 3:44 ` [Bug target/107671] i386: Missed optimization: use of bt in bit test pattern (using -O2 -mtune=core2) ibuclaw at gdcproject dot org 2022-11-14 4:00 ` ibuclaw at gdcproject dot org [this message] 2022-11-15 1:27 ` crazylht at gmail dot com 2022-11-15 13:15 ` ubizjak at gmail dot com 2022-11-15 16:19 ` ibuclaw at gdcproject dot org 2023-11-12 22:41 ` pinskia at gcc dot gnu.org 2023-11-12 22:46 ` 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-107671-4-0l9joILO8X@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).