To fix this without introducing a big lock or breaking compatibility,
this variable is turned into an atomic, and a restriction is introduced
on its mutability: it may only be mutated from false to true, not
from true to false. This allows to ensure that threads can't set this
back to false under the feet of other threads relying on this being
true.
Details
Details
- Reviewers
rriddle
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This is going to turn into an assert soon, whenever I get around to landing: https://reviews.llvm.org/D112021
Comment Actions
Thanks for the quick reply! Great to hear this is going to be resolved in the principled way. I'll switch to fixing the faulty call sites in IREE, then.