[LLVMdev] RFC: Atomics.h

[Burke, Max]

MemoryFence() and MemoryBarrier() are both macros so #undef'ing them should work and if their functionality is needed then the Win32 ReadBarrier/WriteBarrier/ReadWriteBarrier functions (or their underscore-prefixed intrinsics) should be substitutable.

-Max


-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner
Sent: Tuesday, June 02, 2009 10:16 AM
To: LLVM Developers Mailing List
Subject: Re: [LLVMdev] RFC: Atomics.h


On Jun 1, 2009, at 11:17 PM, Jonathan Ragan-Kelley wrote:

> Yes, indeed.

Are they macros or functions?  If macros, why not just #undef them at  
the top of Atomics.h?

-Chris