The current max-stack code does not account for functions that do not have .stack_sizes metadata provided by LLVM. This includes inline assembly (like system calls), statically linked libraries (like from salty), or compiler-builtins (like memcpy).
I've written a hacky pass to the stack analysis to calculate this: james/enhance-stack.../james/calculate-stack. If this analysis appears to be sufficient enough, we could potentially remove our dependency on the unstable -Z flags required to make rustc/llvm emit the .stack_sizes section.
CC #2588
The current max-stack code does not account for functions that do not have
.stack_sizesmetadata provided by LLVM. This includes inline assembly (like system calls), statically linked libraries (like fromsalty), or compiler-builtins (likememcpy).I've written a hacky pass to the stack analysis to calculate this: james/enhance-stack.../james/calculate-stack. If this analysis appears to be sufficient enough, we could potentially remove our dependency on the unstable
-Zflags required to make rustc/llvm emit the.stack_sizessection.CC #2588