[PATCH] D129841: [GlobalOpt] Enable evaluation of atomic stores

[Arthur Eubanks via Phabricator via llvm-commits]

aeubanks added a comment.

+dvyukov

I'm trying to understand if there's any synchronization that can happen between the thread that stores to globals in constructors vs later user threads that come and read globals, or even a later constructor that isn't fully evaluatable. And also how these interact with globals in dlopened shared libraries.
All previous constructors must already have been fully evaluated to get here and we've essentially put a total ordering on loads and stores for evaluated constructors.



================
Comment at: llvm/test/Transforms/GlobalOpt/ctor-list-opt.ll:135
+
+; CHECK-NOT CTOR13
+define internal void @CTOR13() {
----------------
missing colon


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D129841/new/

https://reviews.llvm.org/D129841