public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Arnaud Charlet <charlet@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Vincent Pucci <pucci@adacore.com>
Subject: Re: [Ada] Fix to 64-bit atomic operation failures on ppc-linux
Date: Tue, 17 Jul 2012 11:57:00 -0000	[thread overview]
Message-ID: <50055315.9070306@redhat.com> (raw)
In-Reply-To: <20120717101511.GA25996@adacore.com>

On 07/17/2012 06:15 AM, Arnaud Charlet wrote:
> This patch fixes failures due to the use of 64-bit atomic
> operations on ppc-linux. Undo of the previous patch for 64-bit atomic
> operations only.
>
> Note: this does NOT address the failure on ppc-darwin, which will be addressed
> by another patch soon.
>
> Tested on x86_64-pc-linux-gnu, committed on trunk
>
> 2012-07-17  Vincent Pucci  <pucci@adacore.com>
>
> 	* s-atopri.adb (Lock_Free_Try_Write_X): Atomic_Compare_Exchange_X
> 	replaced by Sync_Compare_And_Swap_X.
> 	(Lock_Free_Try_Write_64): Removed.
> 	* s-atopri.ads (Sync_Compare_And_Swap_X): Replaces previous
> 	routine Atomic_Compare_Exchange_X.
> 	(Lock_Free_Read_64): Renaming of Atomic_Load_64.
> 	(Lock_Free_Try_Write_64): Renaming of Sync_Compare_And_Swap_64.
>
What is the nature of the atomic failures using the 
__atomic_compare_exchange built-in?   Does it have anything to do with 
the expected value being returned by pointer?



Andrew

  reply	other threads:[~2012-07-17 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 10:15 Arnaud Charlet
2012-07-17 11:57 ` Andrew MacLeod [this message]
2012-07-17 15:57   ` Richard Henderson
2012-07-17 15:59     ` Andrew MacLeod
2012-07-17 15:55 ` 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=50055315.9070306@redhat.com \
    --to=amacleod@redhat.com \
    --cc=charlet@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pucci@adacore.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).