MemoryBarrier and MinGW

[Thiago Macieira]

On Friday, 7 de October de 2011 13:57:39 Earnie Boyd wrote:
> Looking into the MSDN documentation for MemoryBarrier brings me to the
> sad conclusion that it is really part of the .NET services and not
> really part of Win32 API.  However the Interlocked services is part of
> the API and should be used while MemoryBarrier should be conditioned.
> 
> http://msdn.microsoft.com/en-us/library/ms684122(v=vs.85).aspx
> 
> These are defined in Winbase.h in MinGW.

http://msdn.microsoft.com/en-us/library/ms684208(VS.85).aspx

It looks like it's part of the Win32 API, even though there's no function with 
that name exported from any DLL. It's always inline or a macro.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20111007/58de9f78/attachment.pgp>