sday, December 5, 2017 2:35 PM
> *To:* Michael Saboff <msab...@apple.com>
> *Cc:* John N. Lehner <jleh...@apple.com>; WebKit-Dev <
> webkit-dev@lists.webkit.org>
> *Subject:* Re: [webkit-dev] Proposal: Do not support Windows fibers
>
>
>
> If our Windows cl
rg>
Subject: Re: [webkit-dev] Proposal: Do not support Windows fibers
If our Windows clients are cool with it, I think we should remove support for
fibers.
I don’t think our current implementation works super well with fibers. It is
best not to include half-working code in the tree.
Geoff
On Dec
If our Windows clients are cool with it, I think we should remove support for
fibers.
I don’t think our current implementation works super well with fibers. It is
best not to include half-working code in the tree.
Geoff
> On Dec 5, 2017, at 11:19 AM, Michael Saboff wrote:
Here is the reply from iTunes for the WebKit-Dev list
- Michael
——
From an iTunes perspective, WebKit can eliminate any remaining Windows Fiber
API support.
iTunes still uses some cooperative threading, but implements its own mechanism
on top of regular preemptive Windows threads. And we
[Bringing John Lehner from the iTunes team into the discussion]
Last I knew, the iTunes team uses fibers. IIRC, the thread they use to call
into WebKit/JSC only has one fiber, other parts of the app use multiple fibers
on one thread but don’t have JS objects active in those threads / fibers.
Yeah, I don't think there is much need to support fibers. With features
like web workers, supporting fibers doesn't make much sense.
- R. Niwa
On Tue, Dec 5, 2017 at 9:44 AM, Yusuke SUZUKI wrote:
> Hi, Webkittens,
>
> I would like to make sure OR declare that WebKit does
Hi, Webkittens,
I would like to make sure OR declare that WebKit does not support Windows
fibers.
While fiber related functions are used in WTF, I believe that it is because
fiber local storage (FLS) can have destructors. And it is not intended to
support fibers explicitly.
Actually, I believe
7 matches
Mail list logo