Re: [webkit-dev] Bring back ARMv6 support to JSC

> On Sep 5, 2017, at 10:51 AM, Olmstead, Don wrote: > > We have plans to add a JSC-Only windows bot in the very near future. Would > that have any bearing on the state of JIT in Windows? Not really. Because of the poor state of that code, I think we should rip it

Re: [webkit-dev] Bring back ARMv6 support to JSC

There isn’t anyone maintaining the 32-not JIT ports to the level of quality we have in our 64-not ports. Making 32-bit use the 64-bit cloop would be a quality progression for actual users of 32-bit. -Filip > On Sep 5, 2017, at 8:02 AM, Adrian Perez de Castro wrote: > >>

Re: [webkit-dev] Bring back ARMv6 support to JSC

On Tue, 5 Sep 2017 16:38:09 +0200, Osztrogonác Csaba wrote: > [...] > > Maybe it will be hard to say good bye to 32-bit architecutres > for many people, but please, it's 2017 now, the first ARMv8 SoC > is out 4 years ago, the first AMD64 CPU is out 14 years ago. While

Re: [webkit-dev] Bring back ARMv6 support to JSC

Hi, I expected exactly this proposal when Apple announced the 64-bit only iOS 11 near 3 months ago. ( I should have bet. :) ) I can understand that 32-bit is only an unnecessary barrier for you and you don't want to bear the maintenance cost of it when there isn't a significant amount of

Re: [webkit-dev] Bring back ARMv6 support to JSC

I think that JIT support on platforms that don’t get regular tuning doesn’t make sense. I think we should: - Remove JIT support for 32-bit platforms - Remove JIT support for Windows - Remove JSVALUE32_64 - Use cloop In 64-bit mode on 32-bit platforms and Windows. I think this approach would be

Re: [webkit-dev] Bring back ARMv6 support to JSC

Hi guys,I've posted this on the bug thread, but I would also like to revive the discussion here. After our last discussion, I put some effort to enable IC for ARMv6 into JIT layers and now I finally collected some results for that. Now, we have regressions just into 2 tests in SunSpider (they