In the following cases, MSan should report specifically what happened, rather
than give a generic use-of-uninitialized-value warning:
- uninitialized value passed as an input parameter to an inline asm block,
- crash within a heuristically handled intrinsic (does this happen at all or do
they always propagate shadow?)
Original issue reported on code.google.com by earth...@google.com on 16 Oct 2014 at 5:18
Original issue reported on code.google.com by
earth...@google.com
on 16 Oct 2014 at 5:18