public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55139] New: __atomic store does not support __ATOMIC_HLE_RELEASE
Date: Tue, 30 Oct 2012 16:59:00 -0000	[thread overview]
Message-ID: <bug-55139-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55139
           Summary: __atomic store does not support __ATOMIC_HLE_RELEASE
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: andi-gcc@firstfloor.org


volatile int slock;

void unlock(void)
{
        int free_val = 1;
        __atomic_store(&slock, &free_val,
__ATOMIC_RELEASE|__ATOMIC_HLE_RELEASE);
}

spin.c: In function 'unlock':
spin.c:6:16: warning: invalid memory model argument 3 of '__atomic_store'
[-Winvalid-memory-model]
  __atomic_store(&slock, &free_val, __ATOMIC_RELEASE|__ATOMIC_HLE_RELEASE);


But XRELEASE MOV ... is allowed in TSX.


             reply	other threads:[~2012-10-30 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 16:59 andi-gcc at firstfloor dot org [this message]
2012-11-07  4:04 ` [Bug target/55139] " andi-gcc at firstfloor dot org
2012-11-07 14:31 ` jakub at gcc dot gnu.org
2012-11-07 14:45 ` andi-gcc at firstfloor dot org
2012-11-09 14:06 ` andi-gcc at firstfloor dot org
2012-11-09 15:24 ` ak at gcc dot gnu.org
2024-04-09  3:22 ` 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-55139-4@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).