TLDR: There is a field in called EMSCRIPTEN_ROOT in the config file
which in theory can be used by external tools to find the "active"
emscripten. I'm proposing to remove it.
---
Maintaining this field has a cost and it can get out of sync with the
emscripten you are actually using.Imagine
LLVM LTO in general should be safe IIUC. At least when using upstream
llvm I don't know of any issues. Perhaps there is something different
with fastcomp that I'm not aware of. Perhaps we should remove that
from the docs.
On Tue, Oct 9, 2018 at 3:34 PM Александр Гурьянов wrote:
>
> Hi. I tried
Hi. I tried it couple of times. Problem is in undefined behaviour my
code works correctly most of time, but sometimes unpredictable erros
are happen. I decide to not use them, because it is impossible to
prove that output is working correctly.
ср, 10 окт. 2018 г. в 0:09, Corey Lucier :
>
> We
We really wish to lean on LLVM link time optimizations.
The Emscripten docs say . "LLVM LTO is not perfectly stable yet, and can
cause code to behave incorrectly.".
Does this note still apply? There's nothing saying what particular
scenarios are problematic and I can't find equivalent docs in
