Bug 43303 – [Qt] Enable JIT on WinCE

• Component: WebKit Qt
• Status: RESOLVED FIXED

[Patrick R. Gansterer]

Enable the JIT on Windows CE with ARM.

[Patrick R. Gansterer]

Created attachment 63156 [details]
Patch #1 (generate GeneratedJITStubs_MSVC.asm)

[Gabor Loki]

Can we combine *_RVCT.h and *_MSVC.asm generation rules? I am not a qmake expert, but I feel they can be merged into a common rule.

[Ismail Donmez]

With this patch if I enable JIT manually I got lots of unresolved functions, one example is;

jscore.lib(JITCall.obj) : error LNK2019: unresolved external symbol cti_op_call_NotJSFunction referenced in function "pr
ivate: void __cdecl JSC::JIT::compileOpCallVarargsSlowCase(struct JSC::Instruction *,struct JSC::SlowCaseEntry * &)" (?c
ompileOpCallVarargsSlowCase@JIT@JSC@@AAAXPAUInstruction@2@AAPAUSlowCaseEntry@2@@Z)
jscore.lib(JITCall.obj) : error LNK2019: unresolved external symbol cti_op_construct_NotJSConstruct referenced in functi
on "private: void __cdecl JSC::JIT::compileOpCallSlowCase(struct JSC::Instruction *,struct JSC::SlowCaseEntry * &,unsign
ed int,enum JSC::OpcodeID)" (?compileOpCallSlowCase@JIT@JSC@@AAAXPAUInstruction@2@AAPAUSlowCaseEntry@2@IW4OpcodeID@2@@Z)

[Eric Seidel (no email)]

Comment on attachment 63156 [details]
Patch #1 (generate GeneratedJITStubs_MSVC.asm)

OK.

[Eric Seidel (no email)]

Since the WinCE port doesn't have a buildbot we won't know if this breaks the world.  But I leave that to you all to figure out.

[Patrick R. Gansterer]

(In reply to comment #3)
> With this patch if I enable JIT manually I got lots of unresolved functions
There are "two steps" in the qt build. First: generate _all_ files Second: only _compile_ and link them.
This pach now only extends the generation part (changes only DerivedSources.pro).

A second patch is required to call armasm.exe with GeneratedJITStubs_MSVC.asm and then link the object file to the JavaScriptCore library.

At the moment you can add the asm file like WebCore/plugins/win/PaintHooks.asm (see WebCore.pro)

(In reply to comment #5)
> Since the WinCE port doesn't have a buildbot we won't know if this breaks the world.  But I leave that to you all to figure out.
I don't think that it will break anything, because it only add an additional generater.
buildbot for WinCE is an interessing topic: A few month ago I tried to run the JSC-test for the "native" WinCE port, but I had many problems with the current scripts. Do they support any sort of "cross-testing" (like cross-comiling ;-))? As far as I know all buildbots build and test on the same machine. Is that correct? (I can only cross-compile for WinCE)

[Ismail Donmez]

(In reply to comment #6)
> (In reply to comment #3)
> > With this patch if I enable JIT manually I got lots of unresolved functions
> There are "two steps" in the qt build. First: generate _all_ files Second: only _compile_ and link them.
> This pach now only extends the generation part (changes only DerivedSources.pro).
> 
> A second patch is required to call armasm.exe with GeneratedJITStubs_MSVC.asm and then link the object file to the JavaScriptCore library.
> 
> At the moment you can add the asm file like WebCore/plugins/win/PaintHooks.asm (see WebCore.pro)

Ok I'll wait for your patch #2 then, or I can create a patch and submit.

Regards.

[Patrick R. Gansterer]

(In reply to comment #7)
> Ok I'll wait for your patch #2 then, or I can create a patch and submit.
Maybe you can try to generate this patch. I will help you if you have any questions.
A good tip is my CMake buildsystem for WinCE at http://gitorious.org/+wincewebkit-developers/webkit/wincewebkit/blobs/wincegdi/JavaScriptCore/CMakeLists.txt#line425

The main "problem" (why I didn't post patch #2) is finding the correct "scopes" in qmake without breaking something else.

[Eric Seidel (no email)]

Comment on attachment 63156 [details]
Patch #1 (generate GeneratedJITStubs_MSVC.asm)

Clearing flags on attachment: 63156

Committed r64933: <http://trac.webkit.org/changeset/64933>

[Eric Seidel (no email)]

All reviewed patches have been landed.  Closing bug.

[Patrick R. Gansterer]

(In reply to comment #10)
> All reviewed patches have been landed.  Closing bug.
Patch #2 is required too.

[Eric Seidel (no email)]

Please open a new bug for new patches.  The commit-queue will automatically close bugs when there are no more patches with r? or r+ on the bug.

Bug numbers are cheap.  No reason to not spend a few for easier reviewability.