search for: pseudocoe

...lt;http://crystal-lang.org/>) and I’m facing an issue with thread local variables. Since the language relies heavily on coroutines, basically the problem is that a function could start running on a thread, get suspended and continue running on a different thread. So, for example, if I have this pseudocoe: 1. read / write thread local variable 2. do some context switch, might resume in a different thread 3. read / write same thread local variable Now the real issue is that when compiling with optimizations, LLVM wont re-read the thread local address, and instead it will rely on the address stored...