From: Richard Henderson <rth@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, meissner@linux.vnet.ibm.com
Subject: [PATCH 0/3] Conversion to __atomic builtins
Date: Sat, 12 Nov 2011 11:07:00 -0000 [thread overview]
Message-ID: <1321080394-16180-1-git-send-email-rth@redhat.com> (raw)
Well, most of it.
The first patch removes two avoidable warnings in rs6000.md.
It seems like we could avoid many more of the remaining, but
those are harder; this one was obvious.
The second patch is a build error. It has appeared on this
list previously, but not yet applied.
The third implements the atomic operations (mostly) as described in
http://www.rdrop.com/users/paulmck/scalability/paper/N2745r.2011.03.04a.html
There are a couple of instances in which the paper doesn't cover the
handling of memory_model_consume, and I made a best guess. These
are indicated by /* ??? */ markers. I would be obliged if someone
could verify what's supposed to happen in these cases. I attempted
to handle them conservatively.
Tested on ppc64-linux, with a reduced set of languages. I could
not get libjava to build for some reason. Missing symbols linking?
Please double-check.
r~
Richard Henderson (3):
rs6000: fix*_trunc insns use nonimmediate_operand
ppc-linux: Fix call to _Unwind_SetGRPtr
rs6000: Rewrite sync patterns for atomic; expand early.
gcc/config/rs6000/rs6000-protos.h | 10 +-
gcc/config/rs6000/rs6000.c | 675 +++++++++++++++++-----------------
gcc/config/rs6000/rs6000.md | 6 +-
gcc/config/rs6000/sync.md | 705 +++++++++--------------------------
libgcc/config/rs6000/linux-unwind.h | 2 +-
5 files changed, 531 insertions(+), 867 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-11-12 6:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 11:07 Richard Henderson [this message]
2011-11-12 11:45 ` [PATCH 2/3] ppc-linux: Fix call to _Unwind_SetGRPtr Richard Henderson
2011-11-12 13:23 ` [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early Richard Henderson
2011-11-14 21:57 ` David Edelsohn
2012-06-09 12:47 ` Eric Botcazou
2012-06-09 16:40 ` Richard Henderson
2012-06-12 2:30 ` David Edelsohn
2012-06-12 13:56 ` Richard Henderson
2012-06-12 17:46 ` Mike Stump
2012-06-12 23:47 ` David Edelsohn
2012-06-13 15:27 ` Richard Henderson
2012-06-12 15:58 ` Richard Henderson
2012-06-12 23:16 ` David Edelsohn
2012-06-13 8:47 ` Richard Guenther
2012-06-13 15:41 ` Richard Henderson
2011-11-12 13:47 ` [PATCH 1/3] rs6000: fix*_trunc insns use nonimmediate_operand Richard Henderson
2011-11-12 15:59 ` [PATCH 0/3] Conversion to __atomic builtins David Edelsohn
2011-11-14 22:43 ` David Edelsohn
2011-11-15 6:01 ` Richard Henderson
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=1321080394-16180-1-git-send-email-rth@redhat.com \
--to=rth@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
/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).