public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: amacleod@redhat.com
Cc: 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: Tue, 08 Nov 2011 20:22:00 -0000	[thread overview]
Message-ID: <201111081954.pA8JsCkW020894@ignucius.se.axis.com> (raw)
In-Reply-To: <4EB7EEDF.1040103@redhat.com> (message from Andrew MacLeod on	Mon, 7 Nov 2011 15:44:47 +0100)

> From: Andrew MacLeod <amacleod@redhat.com>
> Date: Mon, 7 Nov 2011 15:44:47 +0100

> >> On 11/06/2011 07:38 PM, Hans-Peter Nilsson wrote:
> >>> This (formally a change in the range 181027:181034) got me three
> >>> libstdc++ regressions for cris-elf,

> >> yes, I have a final pending patch which didn't make it to the branch
> >> before the merge.  It changes the behaviour of atomic_flag on targets
> >> with no compare_and_swap.  I *think* it will resolve your problem.
> >>
> >> I've attached the early version of the patch which you can try. Its
> >> missing a documentation change I was going to add tomorrow before
> >> submitting, but we can see if it resolves your problem.  Give it a shot
> >> and let me know.
> > Sorry, no it didn't help.  No additional regressions either
> > though, but the undef'd reference changed to two:

> I should also change it so that the compiler issues an error if 
> atomic_thread_fence doesn't resolve to a something since that implies 
> there is no __sync_sychronize() either, which is also minimally expected 
> at this point.  It should never become  an external reference.

JFTR, you already know this; I saw some commits go by that I
thought was addressing this, but didn't, and then I realized
it'd be better to track it using bugzilla, so I entered PR51038.

brgds, H-P

      parent reply	other threads:[~2011-11-08 19:54 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
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 [this message]

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=201111081954.pA8JsCkW020894@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=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).