diff options
| author | Vitaly Buka <vitalybuka@google.com> | 2016-10-26 05:42:30 +0000 |
|---|---|---|
| committer | Vitaly Buka <vitalybuka@google.com> | 2016-10-26 05:42:30 +0000 |
| commit | 64c80b4e39bbd4dc2b1b3b9b0a1be1eaa3f9c7ed (patch) | |
| tree | 08b054a179032bb7f70f45d94dbaad494310ddad /clang/lib/Format/AffectedRangeManager.cpp | |
| parent | f202365910b9c20a30e26f449dbf6f9b49cf774a (diff) | |
| download | bcm5719-llvm-64c80b4e39bbd4dc2b1b3b9b0a1be1eaa3f9c7ed.tar.gz bcm5719-llvm-64c80b4e39bbd4dc2b1b3b9b0a1be1eaa3f9c7ed.zip | |
[CodeGen] Don't emit lifetime intrinsics for some local variables
Summary:
Current generation of lifetime intrinsics does not handle cases like:
```
{
char x;
l1:
bar(&x, 1);
}
goto l1;
```
We will get code like this:
```
%x = alloca i8, align 1
call void @llvm.lifetime.start(i64 1, i8* nonnull %x)
br label %l1
l1:
%call = call i32 @bar(i8* nonnull %x, i32 1)
call void @llvm.lifetime.end(i64 1, i8* nonnull %x)
br label %l1
```
So the second time bar was called for x which is marked as dead.
Lifetime markers here are misleading so it's better to remove them at all.
This type of bypasses are rare, e.g. code detects just 8 functions building
clang (2329 targets).
PR28267
Reviewers: eugenis
Subscribers: beanz, mgorny, cfe-commits
Differential Revision: https://reviews.llvm.org/D24693
llvm-svn: 285176
Diffstat (limited to 'clang/lib/Format/AffectedRangeManager.cpp')
0 files changed, 0 insertions, 0 deletions
