> -Original Message-
> From: stef...@apache.org [mailto:stef...@apache.org]
> Sent: zaterdag 7 december 2013 10:31
> To: comm...@subversion.apache.org
> Subject: svn commit: r1548823 - in
> /subversion/trunk/subversion/libsvn_fs_x: dag.c id.c id.h temp_serializer.c
> temp_serializer.h
>
> -Original Message-
> From: Bert Huijben [mailto:b...@qqmail.nl]
> Sent: vrijdag 6 december 2013 19:14
> To: 'William A. Rowe Jr.'; 'Stefan Fuhrmann'
> Cc: 'APR Developer List'; 'Stefan Fuhrman'; 'Philip Martin'; 'Subversion
> Development'
> Subject: RE: Race condition in APR_DECLARE_LAT
On 07.12.2013 11:00, Bert Huijben wrote:
>
>> -Original Message-
>> From: stef...@apache.org [mailto:stef...@apache.org]
>> Sent: zaterdag 7 december 2013 10:31
>> To: comm...@subversion.apache.org
>> Subject: svn commit: r1548823 - in
>> /subversion/trunk/subversion/libsvn_fs_x: dag.c id.c
I don't think the static function pointer should be declared volatile.
That would mean that for the normal use of the function pointer in the main
part of the program, compiler optimizations of memory address load
reordering would be disabled. It's only operations that require strict
memory orderi
On 07.12.2013 16:04, Daniel Lescohier wrote:
> Second: why use apr_atomic_casptr? Writing a pointer to a memory address
> is already atomic: another thread cannot see a halfway-changed pointer.
You gotta love how people assume the whole world uses a single CPU
architecture.
-- Brane
--
Branko
On 29 nov 2013, at 21:09, Branko Čibej wrote:
> On 29.11.2013 20:42, Ivan Zhakov wrote:
>> On 29 November 2013 22:22, wrote:
>>> Author: brane
>>> Date: Fri Nov 29 18:22:00 2013
>>> New Revision: 1546619
>>>
>>> URL: http://svn.apache.org/r1546619
>>> Log:
>>> * branches/fsfs-ucsnorm/BRANCH-R
6 matches
Mail list logo