[webkit-dev] SquirrelFish Extreme for non x-86 platforms
jrabbani at gmail.com
Thu Dec 25 00:54:51 PST 2008
This way the engine will run without JIT support. However, what to do with
memory allocation functions like VirtualAlloc() that are only available on
Windows? I mean to say, to run on embedded platforms, what alternate has to
exist that may provide the facility of VirtualAlloc(). As far I have seen,
the virtualAlloc() calls can be disabled even on Windows by setting
HAVE_VIRTUAL_ALLOC to 0 in JSC/wtf/Platform.h. However, the garbage
collection implementation uses this particular call inside
JSC/runtime/Collector.cpp irrespective of HAVE_VIRTUAL_ALLOC being 0 or 1.
Any suggestions on this front?
I have built Windows port with HAVE_VIRTUAL_ALLOC set to 0. But the
VirtualAlloc() call inside JSC/runtime/Collector.cpp if replaced with
fastMalloc() causes the WebKit to crash even on Windows.
J R Shah
On Thu, Dec 25, 2008 at 2:22 AM, Maciej Stachowiak <mjs at apple.com> wrote:
> On Dec 24, 2008, at 1:52 PM, Javed Rabbani wrote:
> That means the current JS Engine (SquirrelFish Extreme) can be run on
> embedded/mobile platforms in bytecode mode without JIT. Correct me if I am
> wrong? If I am correct, then how to enable the engine's bytecode mode? There
> are number of ENABLE switches related to current JS engine...
> It should compile with JIT disabled on platforms that do not support the
> - Maciej
> J R Shah
> On Thu, Dec 25, 2008 at 12:49 AM, Maciej Stachowiak <mjs at apple.com> wrote:
>> On Dec 24, 2008, at 6:46 AM, Holger Freyther wrote:
>> On Wednesday 24 December 2008 14:00:19 Javed Rabbani wrote:
>>>> has been reported to work on any embedded, non-x86 platform?
>>> No, the extreme variant is only working on x86 and work on progress on
>> To be more specific:
>> 1) The JS engine should work on any CPU and on most reasonable operating
>> systems in bytecode mode. It's still pretty fast as bytecode - nearly an
>> order of magnitude faster than the old WebKit JS engine.
>> 2) Currently the JIT only fully works on x86 and will soon also work on
>> x86_64 (currently some basic tests pass but neither performance nor
>> correctness are where we want them to be).
>> 3) We are considering ports of the JIT to other CPU architectures. For
>> mobile platforms, it's not entirely clear whether the JIT will turn out to
>> be better than the bytecode interpreter - the memory cost might outweigh the
>> speed benefit.
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev