diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2023-05-15 23:26:58 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2023-05-15 23:26:58 +0000 |
| commit | 34a0c2172b8cdc93daa46ebf186599941baa056e (patch) | |
| tree | 8ee79c9d003bf8422ad185e937b00b2d957ee72e /examples | |
| parent | 1a87f7477abdb033d960a6af63c95a9e0575e670 (diff) | |
| parent | 0c18a13cc056d4d54ca7261289615b2d03769a76 (diff) | |
Merge #1459
1459: rp/multicore: fix undefined behavior in multicore spawn. r=Dirbaio a=Dirbaio
It is UB to pass `entry` to core1 as `&mut`, because core0 keeps an aliasing pointer to that memory region, and actually writes to it (when `spawn_core1` returns, the stack frame gets deallocated and the memory gets reused). This violates noalias requirements.
Added the fence just in case, een though it works without.
bors r+
Co-authored-by: Dario Nieuwenhuis <[email protected]>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions