4109bac330
Currently BlockAddresses store both the Function and the BasicBlock they reference, and the BlockAddress is part of the use list of both the Function and BasicBlock. This is quite awkward, because this is not really a use of the function itself (and walks of function uses generally skip block addresses for that reason). This also has weird implications on function RAUW (as that will replace the function in block addresses in a way that generally doesn't make sense), and causes other peculiar issues, like the ability to have multiple block addresses for one block (with different functions). Instead, I believe it makes more sense to specify only the basic block and let the function be implied by the BB parent. This does mean that we may have block addresses without a function (if the BB is not inserted), but this should only happen during IR construction.
35 lines
955 B
LLVM
35 lines
955 B
LLVM
; RUN: llvm-reduce --abort-on-invalid-reduction --delta-passes=functions --test FileCheck --test-arg --check-prefixes=INTERESTING --test-arg %s --test-arg --input-file %s -o %t
|
|
; RUN: FileCheck --check-prefixes=RESULT --input-file=%t %s
|
|
|
|
; INTERESTING: @blockaddr.table.other
|
|
|
|
; RESULT: @blockaddr.table.other = private unnamed_addr constant [2 x ptr] [ptr inttoptr (i32 1 to ptr), ptr inttoptr (i32 1 to ptr)]
|
|
|
|
|
|
@blockaddr.table.other = private unnamed_addr constant [2 x ptr] [ptr blockaddress(@bar, %L1), ptr blockaddress(@bar, %L2)]
|
|
|
|
|
|
; RESULT-NOT: define i32 @bar(
|
|
define i32 @bar(i64 %arg0) {
|
|
entry:
|
|
%gep = getelementptr inbounds [2 x ptr], ptr @blockaddr.table.other, i64 0, i64 %arg0
|
|
%load = load ptr, ptr %gep, align 8
|
|
indirectbr ptr %load, [label %L2, label %L1]
|
|
|
|
L1:
|
|
%phi = phi i32 [ 1, %L2 ], [ 2, %entry ]
|
|
ret i32 %phi
|
|
|
|
L2:
|
|
br label %L1
|
|
}
|
|
|
|
; RESULT-NOT: @unused
|
|
define void @unused() {
|
|
entry:
|
|
br label %exit
|
|
|
|
exit:
|
|
ret void
|
|
}
|