Stack leak, eventually causing overflow

[hikari-no-yume]

If you do make test and disable the code in tests that makes failed assertions crash, uxnemu eventually complains you've gotten a working-stack overflow. I've also seen this in one of my own programs that has animation with the screen vector. So I assume there's some push/pop mismatch, a stack leak of sorts.

[hikari-no-yume]

Hmm, actually, the integer signedness branch passes almost all the tests now and doesn't have any overflows in that suite. Maybe the bug here was fixed?

[hikari-no-yume]

This still happens for my little animation program. The problem is that the in-memory stack (@rbp) has a leak and eventually overflows and corrupts something, and that leads to a working-stack overflow. The problem is that brk(); in vectors means that the stack pointer is never decremented at the end of a function:

@screen_
  .rbp LDZ2 #0002 SUB2 .rbp STZ2
  (…)
  BRK
  POP2
  #0000
@.L.return.screen
  .rbp LDZ2 #0002 ADD2 .rbp STZ2
  JMP2r

[lynn]

Fixed, I suppose, by overhauling the Varvara vector API and getting rid of brk().