/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 bartoszmilewski.com
C++ atomics and memory ordering | Bartosz Milewski's Programming Cafe
| | darkcoding.net
Rust atomics on x86: How and why ยท Graham King
15.3 parsecs away

Travel
| | Solvitas perambulum
| | questionableengineering.com
Investigation of Memory Dependence Strategies | Questionable Engineering
26.5 parsecs away

Travel
| | Computer ArchitectureInvestigation of Memory Dependence Prediction Strategies with SimpleScalarLorenzo Allas, John Grun, Sanandeesh Kamat 0.0 AbstractA dynamically scheduled processor may default
| | stefansf.de
Why Qualifier Volatile Is Almost Not What You Want in C
14.1 parsecs away

Travel
| | [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.
| | paul.bone.id.au
x86 Addressing Under the Hood - Paul Bone
71.7 parsecs away

Travel
| In this article we take a look at how the operands of x86 instructions are encoded.