Skip to content

Conversation

@kvark
Copy link
Contributor

@kvark kvark commented Jun 6, 2022

Improves #260 and #278 but doesn't resolve them. At least it doesn't completely skip the other accesses now. It only misses their locations, and I don't know why they are not captured.

Kriskras99 added a commit to Kriskras99/ringbeam that referenced this pull request Jul 10, 2025
Loom throws an unclear (and hopefully wrong) error for all the
interleaved tests. It seems to think that the write reference to
the UnsafeCell lasts longer than it does:
```
Causality violation: Concurrent read and write accesses.
    created: /home/kriskras99/Source/ringbeam/src/ring/mod.rs:126:21
       read: thread #1 @ /home/kriskras99/Source/ringbeam/src/ring/recv_values.rs:72:63
```
With [PR loom#279](tokio-rs/loom#279) it also
shows a write in thread #1 but without a location.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant