whoops, sorry, retracting my previous comment, in fact there was an issue in the way our js128 package was built that made it blow on arm64 hardware with CFI protection enabled, which triggered the SIGILL. Once fixed, all basic jit tests pass: ``` /usr/obj/ports/firefox-128.11.0esr.source/firefox-128.11.0/js/src/jit-test/ $python3 jit_test.py ../../../../build-aarch64/dist/bin/js basic [1479| 0| 0| 0] 100% ==========================================>| 21.8s PASSED ALL ``` will run 'all' jit tests, but in the end that doesnt seem a JS engine issue (for now?) and more an xpcom issue with llvm19 ?
Bug 1973016 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
whoops, sorry, retracting my previous comment, in fact there was an issue in the way our js128 package was built that made it blow on arm64 hardware with CFI protection enabled, which triggered the SIGILL. Once fixed, all basic jit tests pass:
```
/usr/obj/ports/firefox-128.11.0esr.source/firefox-128.11.0/js/src/jit-test/ $
python3 jit_test.py ../../../../build-aarch64/dist/bin/js basic
[1479| 0| 0| 0] 100% ==========================================>| 21.8s
PASSED ALL
```
will run 'all' jit tests, but in the end that doesnt seem a JS engine issue (for now?) and more an xpcom issue with llvm19 ?