Explore >> Select a destination
|
You are here 
|
dgraph.io | ||
| | | | |
stefansf.de
|
|
| | | | | [AI summary] The provided text discusses the misuse of the `volatile` keyword in C programming and its inability to address concurrency and memory ordering issues. It explains that `volatile` ensures that compiler optimizations do not remove accesses to variables, but it does not guarantee memory visibility or prevent hardware reordering. The text highlights that `volatile` is only suitable for specific use cases like memory-mapped I/O, and that for thread-safe operations, atomic types and memory barriers are necessary. It also covers examples of how `volatile` can lead to incorrect behavior in multi-threaded programs and how C11's memory model and atomic operations provide a more robust solution. | |
| | | | |
rigtorp.se
|
|
| | | | | This is a short guide describing the latency implications of the virtual memory abstraction. | |
| | | | |
mechanical-sympathy.blogspot.com
|
|
| | | | | When trying to build a highly scalable system the single biggest limitation on scalability is having multiple writers contend for any item o... | |
| | | | |
pewpewthespells.com
|
|
| | | |||
