aboutsummaryrefslogtreecommitdiff
path: root/src/backend/regex/regexec.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2014-09-22 23:35:08 +0200
committerAndres Freund <andres@anarazel.de>2014-09-22 23:35:08 +0200
commit6ba4ecbf477e0b25dd7bde1b0c4e07fc2da19348 (patch)
treec206c338c2dac7026d5010d8b070b8f5911fbe07 /src/backend/regex/regexec.c
parentdf4077cda2eae3eb4a5cf387da0c1e7616e73204 (diff)
downloadpostgresql-6ba4ecbf477e0b25dd7bde1b0c4e07fc2da19348.tar.gz
postgresql-6ba4ecbf477e0b25dd7bde1b0c4e07fc2da19348.zip
Remove most volatile qualifiers from xlog.c
For the reason outlined in df4077cda2e also remove volatile qualifiers from xlog.c. Some of these uses of volatile have been added after noticing problems back when spinlocks didn't imply compiler barriers. So they are a good test - in fact removing the volatiles breaks when done without the barriers in spinlocks present. Several uses of volatile remain where they are explicitly used to access shared memory without locks. These locations are ok with slightly out of date data, but removing the volatile might lead to the variables never being reread from memory. These uses could also be replaced by barriers, but that's a separate change of doubtful value.
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions