This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Use lwsync in PowerPC sync_* builtins

From: Paolo Bonzini <bonzini at gnu dot org>
To: David Edelsohn <dje dot gcc at gmail dot com>
Cc: Anton Blanchard <anton at samba dot org>, Richard Henderson <rth at redhat dot com>, gcc at gcc dot gnu dot org
Date: Thu, 04 Sep 2008 10:11:50 +0200
Subject: Re: [PATCH] Use lwsync in PowerPC sync_* builtins
References: <20080903105728.GA7289@kryten> <48BECA73.9060207@redhat.com> <20080903225342.GB7289@kryten> <303e1d290809031809kd929263rc8c0afd800212e48@mail.gmail.com>

David Edelsohn wrote:
> On Wed, Sep 3, 2008 at 6:53 PM, Anton Blanchard <anton@samba.org> wrote:
>> The only thing lwsync wont order is a store followed by a load. Since
>> the lwsync will always be paired with a store (the stwcx), we will order
>> all accesses before it and provide a release barrier.
> 
> Anton,
> 
> My one other concern is developers using the builtins for applications on
> embedded PowerPC processors.  lwsync will not order accesses to device
> memory space, AFAICT.

Don't you need eieio+sync for that?  GCC does not generate the eieio now.

Paolo

References:
- [PATCH] Use lwsync in PowerPC sync_* builtins
  - From: Anton Blanchard
- Re: [PATCH] Use lwsync in PowerPC sync_* builtins
  - From: Richard Henderson
- Re: [PATCH] Use lwsync in PowerPC sync_* builtins
  - From: Anton Blanchard
- Re: [PATCH] Use lwsync in PowerPC sync_* builtins
  - From: David Edelsohn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]