@@ -38,12 +38,12 @@ extern void pg_spinlock_barrier(void);
38
38
#ifndef pg_compiler_barrier_impl
39
39
/*
40
40
* If the compiler/arch combination does not provide compiler barriers,
41
- * provide a fallback. That fallback simply consists out of a function call
42
- * into a externally defined function. That should guarantee compiler barrier
41
+ * provide a fallback. The fallback simply consists of a function call into
42
+ * an externally defined function. That should guarantee compiler barrier
43
43
* semantics except for compilers that do inter translation unit/global
44
44
* optimization - those better provide an actual compiler barrier.
45
45
*
46
- * Using a native compiler barrier for sure is a lot faster than this...
46
+ * A native compiler barrier for sure is a lot faster than this...
47
47
*/
48
48
#define PG_HAVE_COMPILER_BARRIER_EMULATION
49
49
extern void pg_extern_compiler_barrier (void );
@@ -52,7 +52,7 @@ extern void pg_extern_compiler_barrier(void);
52
52
53
53
54
54
/*
55
- * If we have atomics implementation for this platform fall back to providing
55
+ * If we have atomics implementation for this platform, fall back to providing
56
56
* the atomics API using a spinlock to protect the internal state. Possibly
57
57
* the spinlock implementation uses semaphores internally...
58
58
*
@@ -122,7 +122,7 @@ pg_atomic_unlocked_test_flag_impl(volatile pg_atomic_flag *ptr)
122
122
/*
123
123
* Can't do this efficiently in the semaphore based implementation - we'd
124
124
* have to try to acquire the semaphore - so always return true. That's
125
- * correct, because this is only an unlocked test anyway.Do this in the
125
+ * correct, because this is only an unlocked test anyway. Do this in the
126
126
* header so compilers can optimize the test away.
127
127
*/
128
128
return true;
0 commit comments