TZUTC: -0800
MSGID: 59087.sync_sys@1:103/705 2db61314
PID: Synchronet 3.21a-Linux master/48922a15c Dec 17 2025 GCC 12.2.0
TID: SBBSecho 3.34-Linux master/ffcb56c0e Dec 25 2025 GCC 12.2.0
BBSID: VERT
CHRS: UTF-8 4
FORMAT: flowed
https://gitlab.synchro.net/main/sbbs/-/issues/685#note_8026

> Are there any ARM64/aarch64-specific patches that should be applied but
aren't in the current patch set?

No, all patches are unconditional.

> Is there a known issue with js_GetClassPrototype() on ARM64 with this
version of SpiderMonkey?

No, we haven't seen issues on other systems, and have been using this for
quite a while.

> The build uses `--with-system-nspr` — could there be an incompatibility
between system NSPR (from Debian) and the SpiderMonkey build on ARM64?

I would be very shocked, NSPR4 has been an exceptionally stable API for a very
long time. They do it right, and I trust them a lot.

> Could there be an issue with the libffi ARM64 calling conventions?

The build should be completely replacing the included libffi with the one in
`3rdp/dist` (v3.5.2) before the build. If looking at newer releases of libffi
suggests something has changed, you should be able to test by simply swapping
libffi.tgz out there.

I'll dig into this info, thanks for following up!
--- SBBSecho 3.34-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757
SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 112 134 206 317 400 426 428 470 700 705 240/1120
SEEN-BY: 240/5832 263/1 266/512 280/464 5003 5006 291/111 292/8125
SEEN-BY: 301/1 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58
SEEN-BY: 460/256 1124 633/280 712/848 770/1 902/26 5020/400 8912 5054/30
SEEN-BY: 5075/35
PATH: 103/705 280/464 460/58 229/426