[PATCH] [ASan] Get fake stack code working with GCC 4.8.2.

[Jay Foad]

>>! In D6266#4, @kcc wrote:
> I think that instead of adding an option to one of N supported build systems we need to make the code more compiler-resistant 

Do you mean changing the code in SetShadow? I suppose I could try adding "volatile" or something. (Yuck!)

The only other approach I can think of is for __asan_memset to detect whether it has been called from the application or from libasan itself; either by looking at the return address, or by changing every entry point in the sanitizer to set some "in asan" flag.

http://reviews.llvm.org/D6266