diff options
author | Andy Wingo <wingo@pobox.com> | 2011-05-15 13:22:25 +0200 |
---|---|---|
committer | Andy Wingo <wingo@pobox.com> | 2011-05-15 15:34:16 +0200 |
commit | 6dae2c589b3a6e033cb2109011100d832191a51f (patch) | |
tree | 6cd826bc6e984448f12ee1058cbd5187b310609a | |
parent | 27c6ebcb164e2001306dd6cf82f6beca96133c63 (diff) | |
download | guile-6dae2c589b3a6e033cb2109011100d832191a51f.tar.gz |
remove unused SCM_FENCE definition
* libguile/__scm.h (SCM_FENCE): Remove unused definition.
-rw-r--r-- | libguile/__scm.h | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/libguile/__scm.h b/libguile/__scm.h index c0a546707..0feae02b8 100644 --- a/libguile/__scm.h +++ b/libguile/__scm.h @@ -390,29 +390,6 @@ typedef long SCM_STACKITEM; #define SCM_STACK_PTR(ptr) ((SCM_STACKITEM *) (void *) (ptr)) -/* Anthony Green writes: - When the compiler sees... - DEFER_INTS; - [critical code here] - ALLOW_INTS; - ...it doesn't actually promise to keep the critical code within the - boundries of the DEFER/ALLOW_INTS instructions. It may very well - schedule it outside of the magic defined in those macros. - - However, GCC's volatile asm feature forms a barrier over which code is - never moved. So if you add... - asm (""); - ...to each of the DEFER_INTS and ALLOW_INTS macros, the critical - code will always remain in place. asm's without inputs or outputs - are implicitly volatile. */ -#ifdef __GNUC__ -#define SCM_FENCE asm /* volatile */ ("") -#elif defined (__INTEL_COMPILER) && defined (__ia64) -#define SCM_FENCE __memory_barrier() -#else -#define SCM_FENCE -#endif - #ifdef BUILDING_LIBGUILE #define SCM_TICK SCM_ASYNC_TICK #else |