It's unclear why we allocate ThreadRegistry separately,
I assume it's some historical leftover.
Embed ThreadRegistry into Context.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
compiler-rt/lib/tsan/rtl/tsan_rtl.cpp | ||
---|---|---|
80 | Some strange alignment requirements perhaps? Is I see the same "placeholder" idiom used for Context itself. git blame doesn't lead me very far, so I hope you or Vitaly remember the historical background. |
compiler-rt/lib/tsan/rtl/tsan_rtl.cpp | ||
---|---|---|
80 | Re https://reviews.llvm.org/rGcadbb9241627eefc9f589ae4376fd9ed3e272ecc
Because that's the only way we can allocate anything. We can't declare and use typed global vars.
No, I don't. It was like 10 years ago. I remember initially ThreadRegistry was defined within tsan runtime only, then moved to sanitizer_common and generalized. Lots of things changed at that point. |
Some strange alignment requirements perhaps?
Is
https://reviews.llvm.org/rGcadbb9241627eefc9f589ae4376fd9ed3e272ecc
still relevant? opaque_storage is gone though.
I see the same "placeholder" idiom used for Context itself. git blame doesn't lead me very far, so I hope you or Vitaly remember the historical background.