YAMAMOTO Takashi

> does this disable the following message? > > ``` > libc++abi: bad_alloc was thrown in -fno-exceptions mode > ``` > > while i agree a library should not use...

> Hi @yamt , > > it is really cool that you put so many Wasm runtimes on your benchmarks for comparison! thank you. but honestly speaking i feel i...

> it will be included when i happen to run it again. done. (actually i just pushed an unpushed result i found in local repo.)

> > but honestly speaking i feel i added too many runtimes. > > Yeah maybe you did. I think this benchmark with so many different runtimes could even be...

> > Btw. in order to highlight the strength of the approach you took in your `toywasm` you should definitely also provide benchmarks with other metrics. Namely memory consumption and...

> @yamt thanks to your memory consumption benchmarks I took a better look at `wasmi`'s internal bytecode and was able to make it more space efficient while keeping the original...

> > noted for the next run of the benchmark. > > looking forward :) > > > (probably not too distant future, as i want to see how toywasm...

> > having said that, these "do more work per instruction" style instructions can be rather friendly to interpreters like toywasm because it can hide instruction-fetch-parse overhead. > > At...

> > in toywasm, the value stack cell size depends on build-time configurations. > > ah, that's very interesting and perfect for research about what cell size is the best...

> What just crossed my mind about cell sizes and SIMD support is the following: Maybe it is practical and efficient to have 2 different stacks, e.g. one stack with...