Are multiple copies of a mutable pointer to a shared region of memory always considered undefined behavior?

• nether

  9 6 6.2 Rust

  Bare metal Raspberry Pi 4 Dungeon Keeper clone

I've been rewriting both the math and rasterization code that I'm using in this project for quite some time, because the original (published) code is very naive and slow, consuming 9% of CPU time of the 4 Raspberry Pi cores at 1800MHz to display a single perspective-correct triangle on the screen at 60fps. The problem is that, while rewriting the code, I noticed that my new version will not work with my work-stealing async executor because I require tasks to have the Send trait, and just like in the original code, I'm sharing a mutable frame buffer between all the tasks which is accessed through a mutable pointer, a problem which I accidentally worked around by implementing the Send and Sync traits for the video driver's type which wraps the pointer, potentially hiding undefined behavior in the process.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project