Cheng Shao
Cheng Shao
It seems to me that consumers of debug flavored sysroot will tend to build their own sysroot anyway (with `Debug`, and other custom flags). So simply changing to `Release` seems...
> It does main that anyone who builds a debug binary won't be able to step into any system functions Note that `wasi-libc` is already built sans debug info, and...
Yes, the strip-at-link-time approach is reasonable. It's just that when debug info is enabled (at least via cmake `RelWithDebugInfo` compared to `Release`), the optimization level is lower and that impacts...
Really. See https://github.com/Kitware/CMake/blob/master/Modules/Compiler/GNU.cmake#L59, by default `Release` is `-O3 -DNDEBUG`, while `RelWithDebInfo` is `-O2 -g -DNDEBUG`. And this is another place where `wasi-libc` build flags is inconsistent with the rest of...
One thing I forgot to mention in the previous discussions: shipping sysroots with debug info doesn't really allow one to debug them, because the dwarf sections do not embed the...
> Cabal, i.e. Setup.hs interface doesn't have -j. iirc `Setup build` accepts `-j` argument, and it eventually propagates to `ghc -j` as in [here](https://github.com/haskell/cabal/blob/b32799f13f9665cbfe598b62cbe31a7fa8f6fe74/Cabal/src/Distribution/Simple/Program/GHC.hs#L643). IMO the real problem is `cabal-install`...
> If you use some other high-level build manager, other than cabal-install, why don't you build C sources with something better then Cabal, something which is made for it? Cabal/GHC...
I do believe we need to bump the `autoconf` scripts in this repo. Or land a wasi-specific patch, but that's much less ideal..
@TristanCacqueray I haven't taken a closer look at the examples yet; what kind of `stdin` data do you want to feed into the wasm instance, btw? Is it just a...
@TristanCacqueray So your Haskell logic is a plain loop that polls `stdin`? That wouldn't work as of now, but a feasible workaround is to restructure your `main`, instead of a...