The try builds on linux64 failed due to hg errors, i've asked the rebuild but the linux debug build shows the same failure.
- what is the difference between debug and non debug builds in terms of JIT ? ENABLE_ASSEMBLER and ENABLE_YARR_JIT are set in both on linux, from what i can tell.
- the patch doesnt touch anything under jsgcmark.cpp, and gCurrentCompartment is still initialized to null in jsapi.cpp:JSRuntime::JSRuntime(). The next (and only) initialization of cCurrentCompartment i could find is in jsgc.cpp:AutoGCSession::AutoGCSession(), called from GCCycle() in the same file. Anyway, from your debug session it even seems JSRuntime::JSRuntime() isnt called, since it's not defined to a viable value.
- Any idea why those codepaths seems not used only in debug builds, and only with my changes ?
The try builds on linux64 failed due to hg errors, i've asked the rebuild but the linux debug build shows the same failure.
- what is the difference between debug and non debug builds in terms of JIT ? ENABLE_ASSEMBLER and ENABLE_YARR_JIT are set in both on linux, from what i can tell. JSRuntime: :JSRuntime( ). The next (and only) initialization of cCurrentCompartment i could find is in jsgc.cpp: AutoGCSession: :AutoGCSession( ), called from GCCycle() in the same file. Anyway, from your debug session it even seems JSRuntime: :JSRuntime( ) isnt called, since it's not defined to a viable value.
- the patch doesnt touch anything under jsgcmark.cpp, and gCurrentCompartment is still initialized to null in jsapi.cpp:
- Any idea why those codepaths seems not used only in debug builds, and only with my changes ?