barraclough at apple.com
Sat Jun 23 14:55:08 PDT 2012
As the purpose of the two JITs becomes increasingly coupled it may grow difficult to support the baseline JIT alone without the DFG JIT (we already have a maze of ifdefs for the two JITs, two interpreters, assembler support, value profiling support, etc), so any platforms that want to continue to keep a JIT enabled should probably look into supporting the DFG JIT sooner rather than later.
On Jun 23, 2012, at 7:12 AM, Zoltan Herczeg wrote:
> Good for me. Thanks for helping us. This will help to the buildbot
> maintainers as well, since if a patch cause a break where all of our names
> are CC'ed, they can just disable the JIT until the fix is landed. I think
> the several ports of JSC is something we should be proud of and I hope we
> can keep them in the future.
>> Ah, sorry, I misunderstood!
>> What about having a convention that assembly port maintainers are CC'd on
>> bugs that require new assembler support?
>> This will give you probably 10 hours heads up before the patch lands.
>> On Jun 22, 2012, at 9:29 PM, Zoltan Herczeg <zherczeg at webkit.org> wrote:
>>>> I don't want adding instructions to SH4, MIPS, and legacy ARM to be a
>>>> blocker for JSC work.
>>> I didn't say you have to wait. I just said you should notify us that
>>> something is coming which will break the build.
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev