[webkit-dev] Fall Contributors Meeting?

[Bem Jones-Bey]

Hey all,

At the WebKit contributors meeting, it was mentioned that there was a desire to 
move the meeting to the fall, and potentially having a meeting this fall to 
start that off. Given that fall is rapidly approaching, I figured I'd check in 
to see if there's still a plan for a fall meeting this year, or if it's going 
to be the same plan as usual for 2015.

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

[webkit-dev] Brian Burg is now a WebKit reviewer

[Timothy Hatcher]

Howdy folks!

I’m happy to announce that Brian is now a WebKit reviewer. Brian has been 
working on Web Inspector for a while now — covering both the frontend and the 
backend. His primary focus is integrating his deterministic replay research 
into WebKit and Web Inspector. More on his work can be found at 
http://brrian.org/ http://brrian.org/. Lets hope he has enough time to review 
all of our patches now that he is a new father.

Congratulations on WebKit reviewer and fatherhood, Brian!

— Timothy Hatcher

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

Re: [webkit-dev] Using OfflineAsm

[Vienneau, Christopher]

Thanks for the replies Mark, Michael and Filip.

To follow up:
Michael asks –“What processor(s) and OS(es) are you targeting?”
We are developing on game consoles, our focus is on the ps4 and xboxone.  The 
cpu’s are X86_64, and their OS are ‘similar’ to unix/windows.

Mark wrote – “the C LOOP LLINT emulated a CPU’s behavior using emitted C 
instructions.  As a result, it incurs a performance penalty that is under 10% 
(vs the ASM LLINT) if I remember correctly”
A potential 10% savings is something we’re interested in, we really do want it 
to perform as well as it can within the limitations are working with (no JIT).  
We gave it a quick try since it appeared easy to do but encountered some build 
problems.  We have decided to try again once we re-integrate the recent changes 
from webkit into our codebase.  This will probably be quite some time from now, 
so I’ll pick it up again then.

Thanks again for the help

Chris

From: Mark Lam [mailto:mark@apple.com]
Sent: Friday, September 05, 2014 4:14 PM
To: Vienneau, Christopher
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Using OfflineAsm


On Sep 5, 2014, at 4:05 PM, Mark Lam 
mark@apple.commailto:mark@apple.com wrote:
4)  Should I actually expect a performance increase compared to the “C 
LOOP”?

Yes.  The ASM LLINT should be faster than the C LOOP LLINT.

To clarify, the C LOOP LLINT emulated a CPU’s behavior using emitted C 
instructions.  As a result, it incurs a performance penalty that is under 10% 
(vs the ASM LLINT) if I remember correctly.  So, the perf gain you’ll get comes 
from recuperating the losses due to the C loop being a CPU emulator.  You 
should not expect to see any of the more substantive gains that come from the 
JITs.

Regards,
Mark

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