On Sun, Aug 25, 2019 at 2:21 PM Beuc <[email protected]> wrote:

> Hi,
>
> On Thu, Aug 22, 2019 at 10:18:44AM -0700, 'Sam Clegg' via
> emscripten-discuss wrote:
> > On Thu, Aug 22, 2019 at 8:01 AM Beuc <[email protected]> wrote:
> > > I know about new-asyncify.
> > > However I understood Emterpreter wasn't ported to LLVM "yet", but now
> it seems it won't be at all.
> > > (see also
> https://github.com/emscripten-core/emscripten/issues/9257#issuecomment-523670023
> )
> > > I'd like to know what the official plan is :)
> >
> > I think the idea is that asyncify subsumes all the use cases that
> > Emterpreter previously did.
>
> It looks like no one knows for sure ;)
>
>
I think Sam is right - Asyncify is meant to do everything that Emterpreter
(and old Asyncify) used to do. But more efficiently.

The one thing Emterpreter might do better is the Emterpreter bytecode is
more compact than JS or wasm, so the total download might have been smaller.

> Is there some use case you have that asyncify doesn't handle?
>
> I had answered you in the link above :)
>
> - debug capacity: Emterpreter provides a detailed stack trace whenever
>   trying to pause in the wrong place, which is a must-have to populate
>   the WHITELIST in complex code with indirect calls (e.g. Python);
>   here AFAICT the ASYNCIFY'd application will just skip the
>   emscripten_sleep() and crash mysteriously later.
>
> - pattern-matching in WHITELIST
>   (which I had implemented for Emterpreter)
>
>
Would be good to get issues filed for those things if there aren't already.
(I can try to find time to get to them myself, but not sure when I will be
able to.)

In addition, 1.38.42-upstream fails to compile one of my dependencies:
> https://github.com/emscripten-core/emscripten/issues/9317
> so I cannot do a full-scale test.
>
> More generally, it took me months, lots of reports, lots of patches
> and several work-arounds to get Emterpreter stable enough for
> RenPyWeb's needs.  Consequently I was hoping to avoid doing that again
> and reserve my time for a SDL2 proxy-to-pthread switch/contribution,
> should the time come.
>
> > > Good point about MS Chromium Edge.
> > > I need to test https://www.microsoftedgeinsider.com/
> > >
> > > TBH I'd welcome a working SDL2 proxy-to-pthread (even if it worked
> only for chrome-likes) more than another stack-unwind emulation.
>
> Cheers!
> Sylvain
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/20190825212141.exhiwms2cuxdusb3%40mail.beuc.net
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpSwXX-8P%3DCQhhBr-DXKHQn1wR7kyYTcQ2T7dc6gKhQf%3Dg%40mail.gmail.com.

Reply via email to