mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-07-22 09:29:31 +00:00
e92934e078
It is possible for a global to be substituted with another global of a different type or a different kind (i.e. an alias) at IR link time. One example of this scenario is when a Microsoft ABI vtable is substituted with an alias referring to a larger vtable containing an RTTI reference. This will cause the global to be RAUW'd with a possibly bitcasted reference to the other global. This will of course also affect any references to the global in bitset metadata. The right way to handle such metadata is simply to ignore it. This is sound because the linked module should contain another copy of the bitset entries as applied to the new global. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@240866 91177308-0d34-0410-b5e6-96231b3b80d8
20 lines
472 B
LLVM
20 lines
472 B
LLVM
; RUN: opt -S -lowerbitsets < %s | FileCheck %s
|
|
|
|
target datalayout = "e-p:32:32"
|
|
|
|
; CHECK-NOT: @b = alias
|
|
@a = constant i32 1
|
|
@b = constant [2 x i32] [i32 2, i32 3]
|
|
|
|
!0 = !{!"bitset1", i32* @a, i32 0}
|
|
!1 = !{!"bitset1", i32* bitcast ([2 x i32]* @b to i32*), i32 0}
|
|
|
|
!llvm.bitsets = !{ !0, !1 }
|
|
|
|
declare i1 @llvm.bitset.test(i8* %ptr, metadata %bitset) nounwind readnone
|
|
|
|
define i1 @foo(i8* %p) {
|
|
%x = call i1 @llvm.bitset.test(i8* %p, metadata !"bitset1")
|
|
ret i1 %x
|
|
}
|