cfd2c5ce58
There are two different senses in which a block can be "address-taken". There can be a BlockAddress involved, which means we need to map the IR-level value to some specific block of machine code. Or there can be constructs inside a function which involve using the address of a basic block to implement certain kinds of control flow. Mixing these together causes a problem: if target-specific passes are marking random blocks "address-taken", if we have a BlockAddress, we can't actually tell which MachineBasicBlock corresponds to the BlockAddress. So split this into two separate bits: one for BlockAddress, and one for the machine-specific bits. Discovered while trying to sort out related stuff on D102817. Differential Revision: https://reviews.llvm.org/D124697
31 lines
640 B
YAML
31 lines
640 B
YAML
# RUN: not llc -march=x86-64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
|
|
--- |
|
|
|
|
@addr = global i8* null
|
|
|
|
define void @test() {
|
|
entry:
|
|
store volatile i8* blockaddress(@test, %block), i8** @addr
|
|
%val = load volatile i8*, i8** @addr
|
|
indirectbr i8* %val, [label %block]
|
|
|
|
block:
|
|
ret void
|
|
}
|
|
|
|
...
|
|
---
|
|
name: test
|
|
body: |
|
|
bb.0.entry:
|
|
successors: %bb.1.block
|
|
; CHECK: [[@LINE+1]]:44: expected an IR function reference
|
|
$rax = LEA64r $rip, 1, _, blockaddress(@addr, %ir-block.block), _
|
|
MOV64mr $rip, 1, _, @addr, _, killed $rax
|
|
JMP64m $rip, 1, _, @addr, _
|
|
|
|
bb.1.block:
|
|
RET64
|
|
...
|