RISC-V assembly of a function called memcpy, which just calls itself.

Notices where this attachment appears

1. nil :demisexual_flag: (nil@furry.engineer)'s status on Sunday, 25-Aug-2024 15:59:57 JST nil :demisexual_flag:

   oh my fucking god. so i was having a problem when i enabled optimizations when compiling the doom port. memcpy ended up overwriting itself. so i looked into what was happening, and apparently memcpy just kept calling itself over and over. the reason? i was compiling my own version of memcpy, because i wasn't using the standard library, but i also didn't use the "-ffreestanding" flag, so gcc assumed i *did* have the standard library. so gcc, in its infinite wisdom, saw a memcpy-like pattern in my memcpy and turned it into another call to memcpy, resulting in a stack overflow.