[Interest] Heavily Commented Example: Simple Single Frontend with Two Backends

Giuseppe D'Angelo dangelog at gmail.com
Wed Oct 24 00:22:47 CEST 2012

On 23 October 2012 20:24, Thiago Macieira <thiago.macieira at intel.com> wrote:
> 1) volatile wasn't designed for threading.
> It was designed for memory-mapped I/O

Going slightly off topic, I never managed to find reliable sources
about which problem volatile was meant to solve when it was *first*
introduced: MMIO, changing values from signal handlers (together with
a sig_atomic_t), or saving the value of automatic variables across a
setjmp/longjmp? Of course now it's a reliable solution to all three

(Yes, threads never entered the picture.)

Giuseppe D'Angelo

More information about the Interest mailing list