public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66200] GCC for ARM / AArch64 doesn't define TARGET_RELAXED_ORDERING
Date: Thu, 04 Jun 2015 09:20:00 -0000	[thread overview]
Message-ID: <bug-66200-4-dk3tZViDQI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66200-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Author: ramana
Date: Thu Jun  4 09:19:51 2015
New Revision: 224118

URL: https://gcc.gnu.org/viewcvs?rev=224118&root=gcc&view=rev
Log:
Remove TARGET_RELAXED_ORDERING and optimize for weak memory models.


This patch removes the special casing for targets with relaxed
memory ordering and handles guard accesses with equivalent
atomic load acquire operations. In this process we change the
algorithm to load the guard variable with an atomic load that
has ACQUIRE semantics.

This then means that on targets which have weak memory models, the
fast path is inlined and can directly use a load-acquire instruction
where available (and yay! one more hook gone).

2015-06-04  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        PR c++/66192
        PR target/66200
        * doc/tm.texi: Regenerate.
        * doc/tm.texi.in (TARGET_RELAXED_ORDERING): Delete.
        * target.def (TARGET_RELAXED_ORDERING): Likewise.
        * config/alpha/alpha.c (TARGET_RELAXED_ORDERING): Likewise.
        * config/ia64/ia64.c (TARGET_RELAXED_ORDERING): Likewise.
        * config/rs6000/rs6000.c (TARGET_RELAXED_ORDERING): Likewise.
        * config/sparc/linux.h (SPARC_RELAXED_ORDERING): Likewise.
        * config/sparc/linux64.h (SPARC_RELAXED_ORDERING): Likewise.
        * config/sparc/sparc.c (TARGET_RELAXED_ORDERING): Likewise.
        * config/sparc/sparc.h (SPARC_RELAXED_ORDERING): Likewise.
        * system.h (TARGET_RELAXED_ORDERING): Poison.

2015-06-04  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        PR c++/66192
        PR target/66200
        * cp-tree.h (get_guard_cond): Adjust declaration
        * decl.c (expand_static_init): Use atomic load acquire
        and adjust call to get_guard_cond.
        * decl2.c (build_atomic_load_byte): New function.
        (get_guard_cond): Handle thread_safety.
        (one_static_initialization_or_destruction): Adjust call to
        get_guard_cond.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/alpha/alpha.c
    trunk/gcc/config/ia64/ia64.c
    trunk/gcc/config/rs6000/rs6000.c
    trunk/gcc/config/sparc/linux.h
    trunk/gcc/config/sparc/linux64.h
    trunk/gcc/config/sparc/sparc.c
    trunk/gcc/config/sparc/sparc.h
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/decl.c
    trunk/gcc/cp/decl2.c
    trunk/gcc/doc/tm.texi
    trunk/gcc/doc/tm.texi.in
    trunk/gcc/system.h
    trunk/gcc/target.def


  parent reply	other threads:[~2015-06-04  9:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 10:29 [Bug target/66200] New: " ramana at gcc dot gnu.org
2015-05-19 10:29 ` [Bug target/66200] " ramana at gcc dot gnu.org
2015-06-04  9:20 ` ramana at gcc dot gnu.org [this message]
2015-06-04  9:25 ` ramana at gcc dot gnu.org
2015-06-09  6:46 ` singhai at gcc dot gnu.org
2015-06-10  7:44 ` ramana at gcc dot gnu.org
2015-06-12  9:50 ` ramana at gcc dot gnu.org
2015-06-16 15:27 ` ramana at gcc dot gnu.org
2015-06-24 10:00 ` ramana 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-66200-4-dk3tZViDQI@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).