Re: [webkit-dev] Drop x86 (32bit) JIT backend

[Yusuke Suzuki]

I uploaded the patch for this change.
https://bugs.webkit.org/show_bug.cgi?id=201790 


-Yusuke

> On Sep 13, 2019, at 15:09, Geoffrey Garen  wrote:
> 
> No objection.
> 
> Geoff
> 
>> On Sep 13, 2019, at 1:39 PM, Yusuke Suzuki  wrote:
>> 
>> Hello all,
>> 
>> Now, Xcode no longer has ability to build 32bit binary.
>> Fedora starts dropping x86 32bit kernel shipping.
>> Our x86/x86_64 JIT requires SSE2, so such CPUs can use JIT if they want by 
>> switching x86 to x86_64.
>> And these CPUs are modern enough to run CLoop at high speed.
>> 
>> x86 32bit JIT backend is very complicated and is being a major maintenance 
>> burden.
>> This is due to very few # of registers. Which scatters a lot of isX86 / 
>> CPU(X86) in Baseline, DFG, and Yarr.
>> I’m now planning to optimize some part of Yarr, but x86 YarrJIT is being a 
>> major barrier of such cleanups / optimizations.
>> 
>> So, I would like to propose dropping X86 32bit JIT support.
>> 
>> -Yusuke
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> https://lists.webkit.org/mailman/listinfo/webkit-dev
> 

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Drop x86 (32bit) JIT backend

[Geoffrey Garen]

No objection.

Geoff

> On Sep 13, 2019, at 1:39 PM, Yusuke Suzuki  wrote:
> 
> Hello all,
> 
> Now, Xcode no longer has ability to build 32bit binary.
> Fedora starts dropping x86 32bit kernel shipping.
> Our x86/x86_64 JIT requires SSE2, so such CPUs can use JIT if they want by 
> switching x86 to x86_64.
> And these CPUs are modern enough to run CLoop at high speed.
> 
> x86 32bit JIT backend is very complicated and is being a major maintenance 
> burden.
> This is due to very few # of registers. Which scatters a lot of isX86 / 
> CPU(X86) in Baseline, DFG, and Yarr.
> I’m now planning to optimize some part of Yarr, but x86 YarrJIT is being a 
> major barrier of such cleanups / optimizations.
> 
> So, I would like to propose dropping X86 32bit JIT support.
> 
> -Yusuke
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Emojis for builder vs tester in EWS status-bubbles

[Aakash Jain]

Hi Everyone,

We had this long-standing issue with the EWS bubbles that many engineers were 
confused whether a queue was build-only, test-only or build-and-test.

For e.g.: https://webkit.org/b/152790
Simon Fraser 2016-01-06: "From the EWS bubbles you can't tell if a bot is a 
build-only bot, or a build-and-test bot. All this time I've been assuming that 
GTK was running tests, and that assumption was wrong."


To solve that, we recently added emojis in the status-bubbles. Builder queues 
will only have builder emoji, tester queues will only have tester emoji, and 
build-and-test queues will have both builder and tester emojis. Also, we have 
separated most of the build-and-test queues into separate builder queues and 
tester queues. These changes should help in clarifying which queue does what. 
The emojis we have used are:

Builder: ️ (https://emojipedia.org/hammer-and-wrench/)

Tester:  (https://emojipedia.org/microscope/)

The emoji for tester doesn't feel very appropriate, and I am curious to know if 
anyone has a better suggestion. I previously used 離 
(https://emojipedia.org/test-tube/), but this emoji was added to Unicode last 
year only, and older OSes don't have this emoji. So I switched to the current 
(microscope) emoji in https://webkit.org/b/201532.

Please let me know if anyone has suggestions for better emojis. If not, atleast 
this email would let people know the purpose of these emojis.

Thanks
Aakash
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Drop x86 (32bit) JIT backend

[Yusuke Suzuki]

Hello all,

Now, Xcode no longer has ability to build 32bit binary.
Fedora starts dropping x86 32bit kernel shipping.
Our x86/x86_64 JIT requires SSE2, so such CPUs can use JIT if they want by 
switching x86 to x86_64.
And these CPUs are modern enough to run CLoop at high speed.

x86 32bit JIT backend is very complicated and is being a major maintenance 
burden.
This is due to very few # of registers. Which scatters a lot of isX86 / 
CPU(X86) in Baseline, DFG, and Yarr.
I’m now planning to optimize some part of Yarr, but x86 YarrJIT is being a 
major barrier of such cleanups / optimizations.

So, I would like to propose dropping X86 32bit JIT support.

-Yusuke
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev