Jonathan Immanuel Brachthäuser
Jonathan Immanuel Brachthäuser
As a workaround, I figured out that the configs are stored here: ``` ~/Library/Group Containers/group.com.docker/settings.json ``` Switching back to 6 CPUS via key: ``` { ... "cpus": 6, ... }...
Great that you follow up on this! In the meantime [this paper](http://www.cs.cornell.edu/~yizhou/papers/abseff-popl2019-tr.pdf) has been written. It explains the problem very well and also presents a solution -- which operationally is...
Yes, lexical effect handling very nicely avoids this problem. You are probably also interested in this paper by [Biernacki et al.](https://dl.acm.org/doi/10.1145/3371116) and my own work on the [Effekt language](https://dl.acm.org/doi/10.1145/3428194) where...
Maybe this is something for our LLVM bug hunters @marvinborner and @MattisKra ?
This explains everything, thanks @marvinborner. 1-2 years ago I discussed with @phischu how the erasers should look like and I wished that for cons-lists they would happen to be tail-recursive...
The same will also apply to sharers, btw.
How does this lead to an additional indirection? I would have assumed it would just be an additional offset computation.
Hmm... I expected it to be ``` Load stack pointer -> add offset -> load return address -> add offset ``` but maybe my mental model of how LLVM works...
ok, then the additional indirection makes sense, thanks for the explanation
Is there a way to make the linker happy?