YAMAMOTO Takashi
YAMAMOTO Takashi
> > does it mean that, combining two components into a single component can trigger the check, right? > > Each component's "can be entered" state is tracked independently (as...
> Should we have the wasi target default to lime1 instead? it's a valid solution. my feeling is it's app developers' choice which set of features it targets to though....
> > > Should we have the wasi target default to lime1 instead? > > > > > > it's a valid solution. my feeling is it's app developers' choice...
> Could you comment on the practical impact of this change? Which features in the wasi-libc build are you looking to disable? Or is there some other purpose here? reference-types...
> > i'm not sure if extended-const is ubiquitous among non-web runtimes though. > > It is in some, it's behind a flag in others, and it's expected to be...
i filed https://github.com/llvm/llvm-project/pull/140010 while testing this
> Should we have the wasi target default to lime1 instead? i gave a thought about this a bit. coding-wise, it's trivial to patch llvm to make it a default...
the ci error looks unrelated to this PR ``` Submodule 'src/config' (https://git.savannah.gnu.org/git/config.git) registered for path 'src/config' Submodule 'src/llvm-project' (https://github.com/llvm/llvm-project) registered for path 'src/llvm-project' Submodule 'src/wasi-libc' (https://github.com/WebAssembly/wasi-libc) registered for path 'src/wasi-libc'...
the last push was a conflict resolution
i feel it a bit inconsistent to have skip and oseek while you don't have iseek or seek.