public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59968] Unused BT patterns Date: Tue, 28 Jan 2014 18:16:00 -0000 [thread overview] Message-ID: <bug-59968-4-i2El1FABAJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59968-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59968 --- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> --- For int bar1; void __attribute__((noinline)) foo1 (int y) { if (!(bar1 & (1 << y))) { bar1 |= 1 << y; xxx1 (); } } we generate .cfi_startproc movl bar1(%rip), %eax btl %edi, %eax jnc .L5 rep ret .p2align 4,,10 .p2align 3 .L5: movl $1, %edx movl %edi, %ecx sall %cl, %edx orl %edx, %eax movl %eax, bar1(%rip) jmp xxx1 I expect bts %edi, bar2(%rip) jc .L7 jmp xxx2 .L8: .p2align 4,,10 .p2align 3 .L7: rep ret
next prev parent reply other threads:[~2014-01-28 18:16 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-28 14:38 [Bug target/59968] New: " hjl.tools at gmail dot com 2014-01-28 16:12 ` [Bug target/59968] " hjl.tools at gmail dot com 2014-01-28 16:18 ` hjl.tools at gmail dot com 2014-01-28 16:20 ` ubizjak at gmail dot com 2014-01-28 16:24 ` ubizjak at gmail dot com 2014-01-28 17:48 ` hjl.tools at gmail dot com 2014-01-28 17:59 ` hjl.tools at gmail dot com 2014-01-28 18:16 ` hjl.tools at gmail dot com [this message] 2014-01-28 18:21 ` hjl.tools at gmail dot com 2014-01-28 18:22 ` hjl.tools at gmail dot com 2014-01-28 18:44 ` ubizjak at gmail dot com 2014-01-28 18:47 ` ubizjak at gmail dot com 2014-01-28 22:21 ` hjl.tools at gmail dot com 2014-01-29 0:20 ` hjl.tools at gmail dot com 2014-01-29 0:23 ` hjl.tools at gmail dot com 2014-01-29 17:58 ` hjl.tools at gmail dot com 2014-01-29 20:39 ` hjl.tools at gmail dot com 2021-08-15 5:47 ` 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-59968-4-i2El1FABAJ@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).