public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/49244] no intrinsics to emit 'lock bts' and 'lock btc'
Date: Wed, 01 Jun 2011 06:55:00 -0000	[thread overview]
Message-ID: <bug-49244-4-iZ3FXHUsR8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49244-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh at gcc dot gnu.org,
                   |                            |jakub at gcc dot gnu.org,
                   |                            |rth at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-01 06:54:05 UTC ---
I'm afraid this can't be done in the combiner nor in peephole2 and generally
would be hard to do after expansion, but perhaps it could be done during
expansion or earlier, by folding the (complex) sequence into a new builtin,
preferrably with space in the name to make it inaccessible to users and then
expanding that builtin.


  reply	other threads:[~2011-06-01  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 19:38 [Bug other/49244] New: " desrt at desrt dot ca
2011-06-01  6:55 ` jakub at gcc dot gnu.org [this message]
2011-06-02 23:07 ` [Bug other/49244] " 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
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-iZ3FXHUsR8@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).