mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-26 21:32:10 +00:00
9e81c3bdb2
Remove the command line argument "struct-path-tbaa" since we should not depend on command line argument to decide which format the IR file is using. Instead, we check the first operand of the tbaa tag node, if it is a MDNode, we treat it as struct-path aware TBAA format, otherwise, we treat it as scalar TBAA format. When clang starts to use struct-path aware TBAA format no matter whether struct-path-tbaa is no, and we can auto-upgrade existing bc files, the support for scalar TBAA format can be dropped. Existing testing cases are updated to use the struct-path aware TBAA format. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191538 91177308-0d34-0410-b5e6-96231b3b80d8
14 lines
599 B
LLVM
14 lines
599 B
LLVM
; RUN: opt < %s -tsan -S | FileCheck %s
|
|
; Check that vtable pointer updates 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 void @Foo(i8** nocapture %a, i8* %b) nounwind uwtable {
|
|
entry:
|
|
; CHECK: call void @__tsan_vptr_update
|
|
store i8* %b, i8** %a, align 8, !tbaa !0
|
|
ret void
|
|
}
|
|
!0 = metadata !{metadata !2, metadata !2, i64 0}
|
|
!1 = metadata !{metadata !"Simple C/C++ TBAA", null}
|
|
!2 = metadata !{metadata !"vtable pointer", metadata !1}
|