[Bug sanitizer/55485] probable false positive on __builtin_setjmp/__builtin_longjmp

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55485

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-28 13:47:41 UTC ---
If I understand it right, that clears all shadow memory corresponding to
current thread's stack, rather than trying to figure out into which function it
longjmps and clearing only everything up to that frame, right?  Might then lead
to not reporting failures afterwards.  But sure, we could do that (but I'd
prefer to do it only after the asan/tsan builtins patch is reviewed).  Do you
do that just for noreturn calls?  What about say __builtin_trap () or
__builtin_unreachable ()?
Though in the asan pass they are likely still represented as noreturn calls and
can be handled the same way.