Re: [webkit-dev] Proposal on retiring JIT on Windows

2023-03-25 Thread Kirsling, Ross via webkit-dev
This seems unfortunate and unexpected to me—I thought having a singular Windows port was supposed to mean reduced maintenance burden, since we don't have to divide the number of Windows maintainers into two. Although reconciling FTL with Windows' calling convention is a challenge that no one's

Re: [webkit-dev] Proposal on retiring JIT on Windows

2023-03-25 Thread Yusuke Suzuki via webkit-dev
> How about LLInt? LLInt has some Windows specific code. > Can I revert the change if the JSC team breaks Windows port even though we > have no EWS nor maintainers? I think, ultimately, we cannot guarantee that it is working given that there is no EWS bots running tests on Windows, it means it

Re: [webkit-dev] Proposal on retiring JIT on Windows

2023-03-25 Thread Fujii Hironori via webkit-dev
It sounds reasonable. I don't object to removing Windows JIT support. How about LLInt? LLInt has some Windows specific code. Can I revert the change if the JSC team breaks Windows port even though we have no EWS nor maintainers? On Sun, Mar 26, 2023 at 6:52 AM Yusuke Suzuki via webkit-dev <

[webkit-dev] Proposal on retiring JIT on Windows

2023-03-25 Thread Yusuke Suzuki via webkit-dev
Hello, I would like to propose retiring JIT on Windows JavaScriptCore. Recently, Apple Windows EWS bots get removed. As a result, there is no test-running EWS bots on Windows. This can work for the other part of WebKit since other ports EWS bots are running tests. However this does not work