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/49244] __sync or __atomic builtins will not emit 'lock bts/btr/btc'
Date: Wed, 06 Oct 2021 02:16:00 +0000	[thread overview]
Message-ID: <bug-49244-4-967lmn7XFY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49244-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49244

--- Comment #25 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #24)
> I wanted to look at #c20, but at least my i9-7960X for e.g. lock; btsl $65,
> var
> acts the same as lock; btsl $1, var rather than lock; btsl $1, var+8,
> so maybe #c20 is not possible.

The maximum bit position is 63 for the immediate operand.

  parent reply	other threads:[~2021-10-06  2:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 19:38 [Bug other/49244] New: no intrinsics to emit 'lock bts' and 'lock btc' desrt at desrt dot ca
2011-06-01  6:55 ` [Bug other/49244] " jakub at gcc dot gnu.org
2011-06-02 23:07 ` desrt at desrt dot ca
2012-08-23  9:47 ` [Bug target/49244] " mgorny at gentoo dot org
2021-10-04 14:52 ` [Bug target/49244] __sync or __atomic builtins will not emit 'lock bts/btr/btc' jakub at gcc dot gnu.org
2021-10-06  2:16 ` hjl.tools at gmail dot com [this message]
2021-10-06  8:00 ` jakub at gcc dot gnu.org
2021-11-10  9:17 ` cvs-commit 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-49244-4-967lmn7XFY@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: link
Be 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).