File tree Expand file tree Collapse file tree 3 files changed +3
-23
lines changed Expand file tree Collapse file tree 3 files changed +3
-23
lines changed Original file line number Diff line number Diff line change @@ -40,14 +40,6 @@ pg_spinlock_barrier(void)
40
40
}
41
41
#endif
42
42
43
- #ifdef PG_HAVE_COMPILER_BARRIER_EMULATION
44
- void
45
- pg_extern_compiler_barrier (void )
46
- {
47
- /* do nothing */
48
- }
49
- #endif
50
-
51
43
52
44
#ifdef PG_HAVE_ATOMIC_U64_SIMULATION
53
45
Original file line number Diff line number Diff line change 98
98
#if !defined(PG_HAVE_ATOMIC_U32_SUPPORT )
99
99
#error "could not find an implementation of pg_atomic_uint32"
100
100
#endif
101
+ #if !defined(pg_compiler_barrier_impl )
102
+ #error "could not find an implementation of pg_compiler_barrier"
103
+ #endif
101
104
102
105
/*
103
106
* Provide a spinlock-based implementation of the 64 bit variants, if
Original file line number Diff line number Diff line change @@ -33,21 +33,6 @@ extern void pg_spinlock_barrier(void);
33
33
#define pg_memory_barrier_impl pg_spinlock_barrier
34
34
#endif
35
35
36
- #ifndef pg_compiler_barrier_impl
37
- /*
38
- * If the compiler/arch combination does not provide compiler barriers,
39
- * provide a fallback. The fallback simply consists of a function call into
40
- * an externally defined function. That should guarantee compiler barrier
41
- * semantics except for compilers that do inter translation unit/global
42
- * optimization - those better provide an actual compiler barrier.
43
- *
44
- * A native compiler barrier for sure is a lot faster than this...
45
- */
46
- #define PG_HAVE_COMPILER_BARRIER_EMULATION
47
- extern void pg_extern_compiler_barrier (void );
48
- #define pg_compiler_barrier_impl pg_extern_compiler_barrier
49
- #endif
50
-
51
36
52
37
#if !defined(PG_HAVE_ATOMIC_U64_SUPPORT )
53
38
You can’t perform that action at this time.
0 commit comments