forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit44cd47c
committed
Make fallback implementation of pg_memory_barrier() work.
The fallback implementation involves acquiring and releasing a spinlockvariable that is otherwise unreferenced --- not even to the extent ofinitializing it. This accidentally fails to fail on platforms wherespinlocks should be initialized to zeroes, but elsewhere it results ina "stuck spinlock" failure during startup.I griped about this last July, and put in a hack that worked for gccon HPPA, but didn't get around to fixing the general case. Per thediscussion back then, the best thing to do seems to be to initializedummy_spinlock in main.c.1 parentc1907f0 commit44cd47c
1 file changed
+8
-0
lines changedLines changed: 8 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
37 | 37 |
| |
38 | 38 |
| |
39 | 39 |
| |
| 40 | + | |
| 41 | + | |
40 | 42 |
| |
41 | 43 |
| |
42 | 44 |
| |
| |||
288 | 290 |
| |
289 | 291 |
| |
290 | 292 |
| |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
291 | 299 |
| |
292 | 300 |
| |
293 | 301 |
| |
|
0 commit comments
Comments
(0)