3336f681e3
Summary:
This change adds some verification in the IR verifier around struct path
TBAA metadata.
Other than some basic sanity checks (e.g. we get constant integers where
we expect constant integers), this checks:
- That by the time an struct access tuple `(base-type, offset)` is
"reduced" to a scalar base type, the offset is `0`. For instance, in
C++ you can't start from, say `("struct-a", 16)`, and end up with
`("int", 4)` -- by the time the base type is `"int"`, the offset
better be zero. In particular, a variant of this invariant is needed
for `llvm::getMostGenericTBAA` to be correct.
- That there are no cycles in a struct path.
- That struct type nodes have their offsets listed in an ascending
order.
- That when generating the struct access path, you eventually reach the
access type listed in the tbaa tag node.
Reviewers: dexonsmith, chandlerc, reames, mehdi_amini, manmanren
Subscribers: mcrosier, llvm-commits
Differential Revision: https://reviews.llvm.org/D26438
llvm-svn: 289402
14 lines
502 B
LLVM
14 lines
502 B
LLVM
; RUN: opt < %s -tsan -S | FileCheck %s
|
|
; Check that vptr reads are treated in a special way.
|
|
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
|
|
|
|
define i8 @Foo(i8* %a) nounwind uwtable sanitize_thread {
|
|
entry:
|
|
; CHECK: call void @__tsan_vptr_read
|
|
%0 = load i8, i8* %a, align 8, !tbaa !0
|
|
ret i8 %0
|
|
}
|
|
!0 = !{!2, !2, i64 0}
|
|
!1 = !{!"Simple C/C++ TBAA"}
|
|
!2 = !{!"vtable pointer", !1}
|