In the wake of Geoff's work to simplify threading ifdefs, and Adam's review of
supported ports, I'm curious what people think about maintaining many platform
branches in our WTF and JavaScriptCore threading code.
Right now, it feels rather non-systemic, with some code built upon pthreads, Qt
On Mon, Sep 26, 2011 at 1:47 PM, Alexey Proskuryakov a...@webkit.org wrote:
In the wake of Geoff's work to simplify threading ifdefs, and Adam's review
of supported ports, I'm curious what people think about maintaining many
platform branches in our WTF and JavaScriptCore threading code.
On Mon, Sep 26, 2011 at 10:47 AM, Alexey Proskuryakov a...@webkit.org wrote:
In the wake of Geoff's work to simplify threading ifdefs, and Adam's review
of supported ports, I'm curious what people think about maintaining many
platform branches in our WTF and JavaScriptCore threading code.
On Mon, 26 Sep 2011 14:08:41 -0400, Jarred Nicholls wrote:
Do we want to require that platforms support pthreads, so that code
that isn't performance critical could have just one implementation?
That's the status quo :) MachineStackMarker only works with
pthreads, so QtWin32 and Win ports
Do we want to require that platforms support pthreads, so that code that
isn't performance critical could have just one implementation?
It might work to require either POSIX threads or Win32 threads in all build
configurations, and refactor or remove other threading code.
It's a bit weird to
5 matches
Mail list logo
