Built ROMs cause constant NMI calls

[LambdaCalculus37]

Building any ROMs with any WAD in the current codebase gives me a ROM that, when loaded in ares or Mupen64+, doesn't want to start at all. Looking at the CPU instructions in ares shows a constant string of 'NMI' after a few seconds of loading the ROM, meaning it's hitting a reset loop of sorts.

This is from ROMs built using the unstable branch of libdragon and with gcc 13.2.0. The build environment is running on Debian 13 "Trixie" (currently the testing branch of Debian).