Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Saam Barati
I would also expect bytecode interpreter compilation to be so much faster than JIT compilation that we could laziliy compile either: - When we instantiate - When functions are called for the first time - Saam > On Aug 28, 2018, at 12:17 PM, Yusuke Suzuki > wrote: > > > > On Wed, Aug 29, 201

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
On Wed, Aug 29, 2018 at 4:10 Filip Pizlo wrote: > > On Aug 28, 2018, at 12:09 PM, Yusuke Suzuki > wrote: > > > > On Wed, Aug 29, 2018 at 3:58 Filip Pizlo wrote: > >> >> On Aug 28, 2018, at 11:56 AM, Yusuke Suzuki >> wrote: >> >> >> >> On Wed, Aug 29, 2018 at 3:49 Yusuke Suzuki >> wrote: >> >>

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Filip Pizlo
> On Aug 28, 2018, at 12:09 PM, Yusuke Suzuki > wrote: > > > > On Wed, Aug 29, 2018 at 3:58 Filip Pizlo > wrote: > >> On Aug 28, 2018, at 11:56 AM, Yusuke Suzuki > > wrote: >> >> >> >> On Wed, Aug 29, 2018 at 3:49 Yusuke Suzuki

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
On Wed, Aug 29, 2018 at 3:58 Filip Pizlo wrote: > > On Aug 28, 2018, at 11:56 AM, Yusuke Suzuki > wrote: > > > > On Wed, Aug 29, 2018 at 3:49 Yusuke Suzuki > wrote: > >> >> >> On Wed, Aug 29, 2018 at 3:27 Filip Pizlo wrote: >> >>> >>> On Aug 28, 2018, at 11:25 AM, Yusuke Suzuki >>> wrote: >>>

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Filip Pizlo
> On Aug 28, 2018, at 11:56 AM, Yusuke Suzuki > wrote: > > > > On Wed, Aug 29, 2018 at 3:49 Yusuke Suzuki > wrote: > > > On Wed, Aug 29, 2018 at 3:27 Filip Pizlo > wrote: > >> On Aug 28, 2018, at 11:25 AM, Yusuke Suzuki >

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
On Wed, Aug 29, 2018 at 3:49 Yusuke Suzuki wrote: > > > On Wed, Aug 29, 2018 at 3:27 Filip Pizlo wrote: > >> >> On Aug 28, 2018, at 11:25 AM, Yusuke Suzuki >> wrote: >> >> Thanks! >> >> On Wed, Aug 29, 2018 at 3:22 Filip Pizlo wrote: >> >>> I don’t like this proposal. >>> >>> If we are running

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
On Wed, Aug 29, 2018 at 3:27 Filip Pizlo wrote: > > On Aug 28, 2018, at 11:25 AM, Yusuke Suzuki > wrote: > > Thanks! > > On Wed, Aug 29, 2018 at 3:22 Filip Pizlo wrote: > >> I don’t like this proposal. >> >> If we are running low on memory, we should switch to bounds checked >> memory. >> > > H

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Filip Pizlo
> On Aug 28, 2018, at 11:25 AM, Yusuke Suzuki > wrote: > > Thanks! > > On Wed, Aug 29, 2018 at 3:22 Filip Pizlo > wrote: > I don’t like this proposal. > > If we are running low on memory, we should switch to bounds checked memory. > > How about using bound checking

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
Thanks! On Wed, Aug 29, 2018 at 3:22 Filip Pizlo wrote: > I don’t like this proposal. > > If we are running low on memory, we should switch to bounds checked memory. > How about using bound checking mode exclusively for low environment? > -Filip > > > On Aug 28, 2018, at 11:21 AM, Yusuke Suzu

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Filip Pizlo
I don’t like this proposal. If we are running low on memory, we should switch to bounds checked memory. -Filip > On Aug 28, 2018, at 11:21 AM, Yusuke Suzuki > wrote: > > Posted this mail to webkit-dev mailing list too :) > > On Wed, Aug 29, 2018 at 3:19 AM Yusuke Suzuki

Re: [webkit-dev] Can we drop supporting mixed Wasm::MemoryMode in one process?

2018-08-28 Thread Yusuke Suzuki
Posted this mail to webkit-dev mailing list too :) On Wed, Aug 29, 2018 at 3:19 AM Yusuke Suzuki wrote: > Hi JSC folks, > > In Wasm supported environment, our MemoryMode is a bit dynamic. > When we fail to allocate WasmMemory for signaling mode, we fall back to > the bound checking memory instea