Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThis should say 2010. I believe much of it is out of date, as C11 does have a memory model, and does provide both atomics and barriers. Many, if not most, uses of volatile should probably be replaced by atomics. https://en.cppreference.com/w/c/atomic
There are gaping omissions in this article. There is a need for volatile in portable C programming, in two circumstances: 1. When an asynchronous signal handler modifies a variable that is inspected by the interrupted mainline code (e.g. to set a flag indicating that the signal went off), that variable must be of type "volatile sig_atomic_t". (The article points to some outside discussion by Hans Boehm about this in relation to Unix, but it's not just for Unix; it's in…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 290
- Total comments
- 136
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2010-03-01 | Nine ways to break your systems code using volatile | regehr | 2 | 0 |
| 2010-09-18 | Nine ways to break your systems code using volatile | gnosis | 1 | 0 |
| 2013-12-04 | Nine ways to break your systems code using volatile | dsego | 2 | 0 |
| 2015-12-02 | Ways to break systems code using volatile (2010) | Tomte | 29 | 0 |
| 2019-05-26 | Ways to break your systems code using volatile (2010)First breakout · Best thread | leafario2 | 132 | 73 |
| 2023-10-05 | Nine ways to break your systems code using volatileLatest 20+ point return | luu | 124 | 63 |
