Require compiler barrier support.
Thomas Munro <tmunro@postgresql.org>
Require compiler barrier support. Previously we had a fallback implementation of pg_compiler_barrier() that called an empty function across a translation unit boundary so the compiler couldn't see what it did. That shouldn't be needed on any current systems, and might not even work with a link time optimizer. Since we now require compiler-specific knowledge of how to implement atomics, we should also know how to implement compiler barriers on a hypothetical new system. Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi> Suggested-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/721bf39a-ed8a-44b0-8b8e-be3bd81db748%40technowledgy.de Discussion: https://postgr.es/m/3351991.1697728588%40sss.pgh.pa.us
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/port/atomics.c | modified | +0 −8 |
| src/include/port/atomics/fallback.h | modified | +0 −15 |
| src/include/port/atomics.h | modified | +3 −0 |
Discussion
- Remove last traces of HPPA support 36 messages · 2023-10-19 → 2024-08-01
- Build with LTO / -flto on macOS 20 messages · 2024-06-03 → 2024-07-31