[PATCH] SimplifyCFG: Avoid miscompilations due to removed lifetime intrinsics
Reid Kleckner
rnk at google.com
Wed Jul 30 01:02:45 PDT 2014
On Wed, Jul 30, 2014 at 12:46 AM, Nick Lewycky <nicholas at mxc.ca> wrote:
> Rafael Ávila de Espíndola wrote:
>
>> This is fine by me.
>>
>> I agree with Reid that we need to figure out what to do with the
>> lifetime intrinsics, but lets not miscompile code while we do that.
>>
>
> My proposal is that we should combine lifetime.start and lifetime.end into
> a single intrinsic that means "store undef to through this pointer" but
> doesn't get optimized away like store to undef does. The additional optz'n
> possible from having distinct start and end isn't worth it.
>
Is this enough information for stack coloring to work? Is this enough
information for ASan use-after-scope detection to work? Right now the
start / end calls are easy to map to unpoison / poison in ASan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140730/b1404556/attachment.html>
More information about the llvm-commits
mailing list