public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: joseph@codesourcery.com
Cc: amacleod@redhat.com, hp@axis.com, hp@axis.com,
	gcc-patches@gcc.gnu.org,   libstdc++@gcc.gnu.org,
	bkoz@redhat.com, rth@redhat.com
Subject: Re: cxx-mem-model merge [6 of 9] - libstdc++-v3
Date: Mon, 07 Nov 2011 17:43:00 -0000	[thread overview]
Message-ID: <201111071732.pA7HW2KR017052@ignucius.se.axis.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1111071621160.24579@digraph.polyomino.org.uk>	(joseph@codesourcery.com)

> From: "Joseph S. Myers" <joseph@codesourcery.com>
> Date: Mon, 7 Nov 2011 17:24:04 +0100

> On Mon, 7 Nov 2011, Andrew MacLeod wrote:
> 
> > Actually, this target has no lock free support whatsoever?  ie, no
> > compare_and_swap instruction, nor an implementation of sync_lock_test_and_set
> > and sync_lock_release?
> > 
> > I think the libstdc++ standard now requires the class atomic_flag to be lock
> > free in order to conform (n3242 29.7.2)
> > 
> > So I guess this is the situation which all the atomic tests are not even
> > suppose to be run since they aren't supported.  My guess is that in the
> > previous releases the c++ header files probably provided a locked
> > implementation of test_and_set, and so the tests would run.
> 
> For bare-metal targets there should maybe be an option to presume there is 
> just one thread and map all atomic operations to dumb non-atomic versions, 
> which is perfectly valid in such a case.  But that's a new feature; we 
> didn't have it for __sync_* either.

It'd not be a new feature, that's apparently how it worked until
it broke now ...unless you mean something different.

brgds, H-P

  parent reply	other threads:[~2011-11-07 17:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 23:52 Andrew MacLeod
2011-11-04 18:17 ` Jeff Law
2011-11-04 18:53   ` Andrew MacLeod
2011-11-07  0:54 ` Hans-Peter Nilsson
2011-11-07  4:48   ` Andrew MacLeod
2011-11-07 11:36     ` Hans-Peter Nilsson
2011-11-07 14:41       ` Andrew MacLeod
2011-11-07 14:56       ` Andrew MacLeod
2011-11-07 15:38         ` Hans-Peter Nilsson
2011-11-07 16:28         ` Joseph S. Myers
2011-11-07 17:24           ` Andrew MacLeod
2011-11-07 17:43           ` Hans-Peter Nilsson [this message]
2011-11-07 18:27             ` Andrew MacLeod
2011-11-08  6:45               ` Hans-Peter Nilsson
2011-11-08 13:43                 ` Andrew MacLeod
2011-11-11 17:49                   ` Benjamin Kosnik
2011-11-11 17:56                     ` Andrew MacLeod
2011-11-11 21:07                       ` Hans-Peter Nilsson
2011-11-11 23:34                       ` Torvald Riegel
2011-11-11 20:27                     ` Hans-Peter Nilsson
2011-11-07 16:32         ` Richard Henderson
2011-11-08 20:22         ` Hans-Peter Nilsson

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=201111071732.pA7HW2KR017052@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=amacleod@redhat.com \
    --cc=bkoz@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@axis.com \
    --cc=joseph@codesourcery.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=rth@redhat.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).