@uint8_t The alternate side of that is "_yo, I heard you had a table of function pointers, so I left all of the pointed at function in the firmware_", which both uses extra space and increases the attack surface for adversaries to exploit.
@th turns out the compiler wasn't doing anything it shouldn't have; turns out I was using the vendor-provided startup code which referenced different function names than opencm3
got rid of the startup asm and cm3's vector.c does the job
@th turns out the compiler wasn't doing anything it shouldn't have; turns out I was using the vendor-provided startup code which referenced different function names than opencm3
got rid of the startup asm and cm3's vector.c does the job