Re: [blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread Manuel Rego Casasnovas 
LGTM3

On 15/02/2023 18:16, Yoav Weiss wrote:
> LGTM2
> 
> On Wed, Feb 15, 2023 at 6:10 PM Chris Harrelson  > wrote:
> 
> LGTM1
> 
> On Wed, Feb 15, 2023 at 8:09 AM 'Thibaud Michaud' via blink-dev
> mailto:blink-dev@chromium.org>> wrote:
> 
> 
> 
> /Web developers/: No signals
> 
> 
> Have you tried to gather signals? Are there developers
> involved in the WASM process? (if so, the phase can count as
> a signal for them as well).
> 
>  
> Maybe Leaning Tech qualifies: they develop an x86 virtualization
> technology using wasm. They have written publicly about their
> use case for tail calls (here
> 
> ,
>  here  and here 
> ), 
> and unblocked the move to phase 4 by implementing it in WebKit (here 
> ).
> 
> 
> /Other signals/:
> 
> 
> WebView application risks
> 
> Does this intent deprecate or change behavior of
> existing APIs, such that it has potentially high risk
> for Android WebView-based applications?
> 
> 
> I'm guessing the answer here is "no"?
> 
>  
> Indeed. 
> 
> -- 
> You received this message because you are subscribed to the
> Google Groups "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to blink-dev+unsubscr...@chromium.org
> .
> To view this discussion on the web visit
> 
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNYfhC78Juo%3DBg%2Bp8OD77A4%3Dha7nU%2BCcXFe58R%3DX%2BmrUHA%40mail.gmail.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to blink-dev+unsubscr...@chromium.org
> .
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXXb6vc70PVuAfCe5adMxsRy0OPGrqBX8gqrun5iD8KvQ%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/518ec509-e51e-c25d-49bf-1597a6d67708%40igalia.com.

Re: [blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread Yoav Weiss 
LGTM2

On Wed, Feb 15, 2023 at 6:10 PM Chris Harrelson 
wrote:

> LGTM1
>
> On Wed, Feb 15, 2023 at 8:09 AM 'Thibaud Michaud' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>>
>>
 *Web developers*: No signals

>>>
>>> Have you tried to gather signals? Are there developers involved in the
>>> WASM process? (if so, the phase can count as a signal for them as well).
>>>
>>
>> Maybe Leaning Tech qualifies: they develop an x86 virtualization
>> technology using wasm. They have written publicly about their use case for
>> tail calls (here
>> ,
>> here  and here
>> ),
>> and unblocked the move to phase 4 by implementing it in WebKit (here
>> ).
>>
>>
 *Other signals*:

 WebView application risks

 Does this intent deprecate or change behavior of existing APIs, such
 that it has potentially high risk for Android WebView-based applications?

>>>
>>> I'm guessing the answer here is "no"?
>>>
>>
>> Indeed.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNYfhC78Juo%3DBg%2Bp8OD77A4%3Dha7nU%2BCcXFe58R%3DX%2BmrUHA%40mail.gmail.com
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXXb6vc70PVuAfCe5adMxsRy0OPGrqBX8gqrun5iD8KvQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread Chris Harrelson 
LGTM1

On Wed, Feb 15, 2023 at 8:09 AM 'Thibaud Michaud' via blink-dev <
blink-dev@chromium.org> wrote:

>
>
>>> *Web developers*: No signals
>>>
>>
>> Have you tried to gather signals? Are there developers involved in the
>> WASM process? (if so, the phase can count as a signal for them as well).
>>
>
> Maybe Leaning Tech qualifies: they develop an x86 virtualization
> technology using wasm. They have written publicly about their use case for
> tail calls (here
> ,
> here  and here
> ),
> and unblocked the move to phase 4 by implementing it in WebKit (here
> ).
>
>
>>> *Other signals*:
>>>
>>> WebView application risks
>>>
>>> Does this intent deprecate or change behavior of existing APIs, such
>>> that it has potentially high risk for Android WebView-based applications?
>>>
>>
>> I'm guessing the answer here is "no"?
>>
>
> Indeed.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNYfhC78Juo%3DBg%2Bp8OD77A4%3Dha7nU%2BCcXFe58R%3DX%2BmrUHA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw84uCh9CHBX3_cUPQ94HkJzzVNjARpjG3zfCZkR984XWA%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread 'Thibaud Michaud' via blink-dev 
>
>> *Web developers*: No signals
>>
>
> Have you tried to gather signals? Are there developers involved in the
> WASM process? (if so, the phase can count as a signal for them as well).
>

Maybe Leaning Tech qualifies: they develop an x86 virtualization technology
using wasm. They have written publicly about their use case for tail calls (
here
,
here  and here
),
and unblocked the move to phase 4 by implementing it in WebKit (here
).


>> *Other signals*:
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>
> I'm guessing the answer here is "no"?
>

Indeed.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNYfhC78Juo%3DBg%2Bp8OD77A4%3Dha7nU%2BCcXFe58R%3DX%2BmrUHA%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread Yoav Weiss 
On Wed, Feb 15, 2023 at 12:17 PM 'Thibaud Michaud' via blink-dev <
blink-dev@chromium.org> wrote:

> Contact emails...@chromium.org, thiba...@chromium.org
>
> Explainer
> https://github.com/WebAssembly/tail-call/blob/main/proposals/tail-call/Overview.md
>
> Specificationhttps://github.com/WebAssembly/tail-call
>
> Design docs
>
> https://github.com/WebAssembly/tail-call/blob/master/proposals/tail-call/Overview.md
>
> Summary
>
> Add an explicit tail call and indirect tail call opcodes to WebAssembly.
>
>
> Blink componentBlink>JavaScript>WebAssembly
> 
>
> Search tagswasm , webassembly
> , tail call
> 
>
> TAG reviewNot required for non cross-cutting WebAssembly features.
>
> TAG review statusNot applicable
>
> Risks
>
>
> Interoperability and Compatibility
>
>
>
> *Gecko*: Positive
>
> *WebKit*: Positive
>

The WASM proposals page suggests this is phase 4
,
which indeed counts as a positive signal.


> *Web developers*: No signals
>

Have you tried to gather signals? Are there developers involved in the WASM
process? (if so, the phase can count as a signal for them as well).


>
> *Other signals*:
>
> WebView application risks
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
>

I'm guessing the answer here is "no"?


>
>
> Debuggability
>
> Yes, using DevTools.
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?Yes
>
> Is this feature fully tested by web-platform-tests
> 
> ?It is tested by WebAssembly spec tests
>
> Flag nameV8: --experimental-wasm-return-call
> Chrome: Features::kWebAssemblyTailCall
>
> Requires code in //chrome?False
>
> Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=7431
>
> Launch bughttps://launch.corp.google.com/launch/4232322
>
> Estimated milestones
>
> 112
>
> Anticipated spec changes
>
> N/A
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5423405012615168
>
> This intent message was generated by Chrome Platform Status
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNbxwBdi84BqEs59Fks7EX9mQdkwRfzqpNoJuC1-5qCejw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWrT6pm7scDkPTVFDv5Ly%3DgzwseDeSzaX5etYOOprbFMQ%40mail.gmail.com.

[blink-dev] Intent to Ship: WebAssembly Tail Call

2023-02-15 Thread 'Thibaud Michaud' via blink-dev 
Contact emails...@chromium.org, thiba...@chromium.org

Explainer
https://github.com/WebAssembly/tail-call/blob/main/proposals/tail-call/Overview.md

Specificationhttps://github.com/WebAssembly/tail-call

Design docs
https://github.com/WebAssembly/tail-call/blob/master/proposals/tail-call/Overview.md

Summary

Add an explicit tail call and indirect tail call opcodes to WebAssembly.


Blink componentBlink>JavaScript>WebAssembly


Search tagswasm , webassembly
, tail call


TAG reviewNot required for non cross-cutting WebAssembly features.

TAG review statusNot applicable

Risks


Interoperability and Compatibility



*Gecko*: Positive

*WebKit*: Positive

*Web developers*: No signals

*Other signals*:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?



Debuggability

Yes, using DevTools.

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests

?It is tested by WebAssembly spec tests

Flag nameV8: --experimental-wasm-return-call
Chrome: Features::kWebAssemblyTailCall

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=7431

Launch bughttps://launch.corp.google.com/launch/4232322

Estimated milestones

112

Anticipated spec changes

N/A

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5423405012615168

This intent message was generated by Chrome Platform Status
.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNbxwBdi84BqEs59Fks7EX9mQdkwRfzqpNoJuC1-5qCejw%40mail.gmail.com.