English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

The C/C++ memory model provides an interface and execution model forprogrammers of concurrent (shared-variable) code. It provides a range ofmechanisms that abstract from underlying hardware memory models -- that governhow multicore architectures handle concurrent accesses to main memory -- aswell as abstracting from compiler transformations. The C standard describes thememory model in terms of cross-thread relationships between events, and hasbeen influenced by several research works that are similarly based. In thispaper we provide a thread-local definition of the fundamental principles of theC memory model, which, for concise concurrent code, serves as a basis forrelatively straightforward reasoning about the effects of the C orderingmechanisms. We argue that this definition is more practical from a programmingperspective and is amenable to analysis by already established techniques forconcurrent code. The key aspect is that the memory model definition is separateto other considerations of a rich programming language such as C, inparticular, expression evaluation and optimisations, though we show how toreason about those considerations in the presence of C concurrency. A majorsimplification of our framework compared to the description in the C standardand related work in the literature is separating out considerations around the"lack of multicopy atomicity", a concept that is in any case irrelevant todevelopers of code for x86, Arm, RISC-V or SPARC architectures. We show how theframework is convenient for reasoning about well-structured code, and forformally addressing unintuitive behaviours such as "out-of-thin-air" writes.

Separation of concerning things: a simpler basis for defining and programming with the C/C++ memory model (extended version)