[PATCH] Implement variable-sized alloca instrumentation (take 2).
tetra2005 at gmail.com
Tue Jan 27 21:50:58 PST 2015
> OMG. I am curious, if you really have targets for which testing alloca is important...
Well, bugs do pop up in various OSS projects. Alloca is surprisingly widespread.
> Do we really need a list here?
> Can't we handle the task with an integer indicating the combined sizes of allocas?
We could simply memset(0) all shadow memory corresponding to dynamic part of stack. But this wouldn't scale to use-after-return (as I understand alloca regions will not be consecutive in this case).
More information about the llvm-commits