public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ak at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55139] __atomic store does not support __ATOMIC_HLE_RELEASE
Date: Fri, 09 Nov 2012 15:24:00 -0000	[thread overview]
Message-ID: <bug-55139-4-92j7HQ0qCm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55139-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from ak at gcc dot gnu.org 2012-11-09 15:24:32 UTC ---
Author: ak
Date: Fri Nov  9 15:24:25 2012
New Revision: 193363

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193363
Log:
Handle target specific memory models in C frontend

get_atomic_generic_size would error out for
__atomic_store(...,__ATOMIC_HLE_RELEASE)

Just mask it out. All the memory orders are checked completely
in builtins.c anyways.

I'm not sure what that check is for, it could be removed in theory.

Passed bootstrap and test suite on x86-64

gcc/c-family/:
2012-11-09  Andi Kleen  <ak@linux.intel.com>

    PR 55139
    * c-common.c (get_atomic_generic_size): Mask with
        MEMMODEL_MASK

Modified:
    trunk/gcc/c-family/ChangeLog
    trunk/gcc/c-family/c-common.c


  parent reply	other threads:[~2012-11-09 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 16:59 [Bug target/55139] New: " andi-gcc at firstfloor dot org
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 [this message]
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-92j7HQ0qCm@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).