/explore
|
You are here 
|
preshing.com | ||
| | | | |
www.internalpointers.com
Synchronizing threads at a lower level. |
|
| | | | | ||
| | | | |
www.nickwilcox.com
With Apple's recent announcement that they are moving away from Intel X86 CPU's to their own ARM CPU's for future laptops and desktops I thought it would be a good time to take a look at the some differences that can affect systems programmers working in Rust. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
ricardomartins.cc
UnsafeCell is the keystone for building interior mutability types in Rust, such as Cell, RefCell, RwLock and Mutex. In this article we'll explore how it works and how it is used by those types. |
|
| | | |||
