public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: rdsandiford@googlemail.com,	richard.earnshaw@arm.com,
	dave.anglin@nrc-cnrc.gc.ca,	kkojima@gcc.gnu.org
Subject: [cxx-mem-model 0/2] Support the legacy __sync libcalls
Date: Thu, 03 Nov 2011 23:27:00 -0000	[thread overview]
Message-ID: <1320362654-20244-1-git-send-email-rth@redhat.com> (raw)

Not installing to the branch because amacleod is busy preparing
the merge.  This can be committed after that's done.

Something similar to the second patch needs to be done for:

  sh[34]-linux
  hppa-linux
  mips16

Given that it's a matter of two lines for each target, the most
important of which is some port-specific condition, I'm going to
leave these to the respective port maintainers.


r~



Richard Henderson (2):
  Allow libcalls to be installed for legacy __sync optabs.
  arm: Install __sync libfuncs for Linux.

 gcc/builtins.c       |    2 +-
 gcc/config/arm/arm.c |    4 +
 gcc/genopinit.c      |   28 +++---
 gcc/omp-low.c        |    4 +-
 gcc/optabs.c         |  217 +++++++++++++++++++++++++++++++++++++++-----------
 gcc/optabs.h         |   99 ++++++++++++-----------
 6 files changed, 241 insertions(+), 113 deletions(-)

-- 
1.7.6.4

             reply	other threads:[~2011-11-03 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 23:27 Richard Henderson [this message]
2011-11-03 23:31 ` [cxx-mem-model 1/2] Allow libcalls to be installed for legacy __sync optabs Richard Henderson
2011-11-03 23:37 ` [cxx-mem-model 2/2] arm: Install __sync libfuncs for Linux Richard Henderson
2011-11-24  1:10   ` Richard Henderson
2011-11-24 10:43     ` Richard Earnshaw
2011-11-24 20:33       ` 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=1320362654-20244-1-git-send-email-rth@redhat.com \
    --to=rth@redhat.com \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kkojima@gcc.gnu.org \
    --cc=rdsandiford@googlemail.com \
    --cc=richard.earnshaw@arm.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).