Hello,
LLINT C Loop implementation is a pure JS interpretation mode, so you can't
enable along with JIT. But LLINT with assembly back-end is intended to have
both JIT(baseline & DFG) and interpreter mode simultaneously. The main goal
of LLINT assembly backend is for JIT emulation, so that code run
Hello!
I tried to compile JSC with LLInt CLoop backend and JIT but it didn't
work for me. I tried it on Mac and Linux as well.
When I looked into it a little I saw some strange guards like this:
Source/JavaScriptCore/llint/LLIntOpcode.h
#if ENABLE(LLINT_C_LOOP)
#define FOR_EACH_LLINT_NOJIT_N
Awesome, thanks for the detailed response.
I did not realize that going to the assembly backend would not produce
a substantial improvement. But after you explanation, I can see the
reasons.
I'll do some more testing to see the impact. If I see it to
be worthwhile and I can fix it, I'll submit
Yes. You can use the assembly LLInt backend without using the JIT. That's how
I was running it when I first wrote it.
I think that the code in Platform.h is being conservative, in the sense that it
assumes that if ENABLE(JIT) is not set then you're compiling for a target that
the LLInt wouldn
LowLevelInterpreter.asm is processed to create LLIntAssembly.h for the
built platform. It appears that if there is no jitting configured[1], this
will always create the C Loop.
Is there any way of using the assembly backends to create LLIntAssembly.h
when not jitting?
[1]: Source/WTF/wtf/Platfor
5 matches
Mail list logo
