Closed xen0n closed 4 days ago
For now a workaround may be disabling JIT in gjs, by calling JS::DisableJitBackend()
before creating the first context/runtime (and before JS_Init*
).
By the way, does make -C js/src check-jit-test JITTEST_EXTRA_ARGS="--timeout 300 -j6"
in SpiderMonkey succeed? Replace "6" with floor(the amount of available memory / 3GB).
Triage: dev-lang/spidermonkey-115.14.0
with USE=jit
unmasked and enabled passes all tests, and dev-libs/gjs-1.80.2
passes tests with it. Maybe it's just some petty toolchain or mozjs bugs that got fixed in the meantime.
Closing :tada:
SpiderMonkey JIT is now enabled in Gentoo.
Causing GNOME3 session to fail to start, among other undiscovered issues.