Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
3dfce376
Commit
3dfce376
authored
Jan 13, 2015
by
Heikki Linnakangas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos in comment.
Plus some tiny wordsmithing of not-quite-typos.
parent
7391e251
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
src/include/port/atomics/fallback.h
src/include/port/atomics/fallback.h
+5
-5
No files found.
src/include/port/atomics/fallback.h
View file @
3dfce376
...
...
@@ -38,12 +38,12 @@ extern void pg_spinlock_barrier(void);
#ifndef pg_compiler_barrier_impl
/*
* If the compiler/arch combination does not provide compiler barriers,
* provide a fallback.
That fallback simply consists out of a function call
*
into a
externally defined function. That should guarantee compiler barrier
* provide a fallback.
The fallback simply consists of a function call into
*
an
externally defined function. That should guarantee compiler barrier
* semantics except for compilers that do inter translation unit/global
* optimization - those better provide an actual compiler barrier.
*
*
Using a
native compiler barrier for sure is a lot faster than this...
*
A
native compiler barrier for sure is a lot faster than this...
*/
#define PG_HAVE_COMPILER_BARRIER_EMULATION
extern
void
pg_extern_compiler_barrier
(
void
);
...
...
@@ -52,7 +52,7 @@ extern void pg_extern_compiler_barrier(void);
/*
* If we have atomics implementation for this platform fall back to providing
* If we have atomics implementation for this platform
,
fall back to providing
* the atomics API using a spinlock to protect the internal state. Possibly
* the spinlock implementation uses semaphores internally...
*
...
...
@@ -122,7 +122,7 @@ pg_atomic_unlocked_test_flag_impl(volatile pg_atomic_flag *ptr)
/*
* Can't do this efficiently in the semaphore based implementation - we'd
* have to try to acquire the semaphore - so always return true. That's
* correct, because this is only an unlocked test anyway.Do this in the
* correct, because this is only an unlocked test anyway.
Do this in the
* header so compilers can optimize the test away.
*/
return
true
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment