Intrinsics are invalid there, code is generated in such way that variable
is being accessed after lifetime.end.
I suspect that optimizer can make invalid code because of this, but I can't
So I think it's safer to remove them at all and don't wait for miscompile
Still if performance is greater concern then potential miscompiles, I can
limit this only to asan-use-after-scope.
On Wed, Sep 21, 2016 at 8:49 AM Akira Hatanaka <ahata...@gmail.com> wrote:
> ahatanak added a comment.
> Do we want to remove lifetime intrinsics when we aren't doing the
> asan-use-after-scope check? Since this isn't a mis-compile caused by
> inaccurate lifetime intrinsics, I was wondering whether we should do this
> only when asan-use-after-scope is on to minimize the impact on compile time.
cfe-commits mailing list