mirror of
https://github.com/RPCSX/llvm.git
synced 2025-02-04 19:38:22 +00:00
5d09c2f25d
This commit modifies the way the machine basic blocks are serialized - now the
machine basic blocks are serialized using a custom syntax instead of relying on
YAML primitives. Instead of using YAML mappings to represent the individual
machine basic blocks in a machine function's body, the new syntax uses a single
YAML block scalar which contains all of the machine basic blocks and
instructions for that function.
This is an example of a function's body that uses the old syntax:
body:
- id: 0
name: entry
instructions:
- '%eax = MOV32r0 implicit-def %eflags'
- 'RETQ %eax'
...
The same body is now written like this:
body: |
bb.0.entry:
%eax = MOV32r0 implicit-def %eflags
RETQ %eax
...
This syntax change is motivated by the fact that the bundled machine
instructions didn't map that well to the old syntax which was using a single
YAML sequence to store all of the machine instructions in a block. The bundled
machine instructions internally use flags like BundledPred and BundledSucc to
determine the bundles, and serializing them as MI flags using the old syntax
would have had a negative impact on the readability and the ease of editing
for MIR files. The new syntax allows me to serialize the bundled machine
instructions using a block construct without relying on the internal flags,
for example:
BUNDLE implicit-def dead %itstate, implicit-def %s1 ... {
t2IT 1, 24, implicit-def %itstate
%s1 = VMOVS killed %s0, 1, killed %cpsr, implicit killed %itstate
}
This commit also converts the MIR testcases to the new syntax. I developed
a script that can convert from the old syntax to the new one. I will post the
script on the llvm-commits mailing list in the thread for this commit.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@244982 91177308-0d34-0410-b5e6-96231b3b80d8
36 lines
819 B
YAML
36 lines
819 B
YAML
# RUN: llc -march=x86-64 -start-after branch-folder -stop-after branch-folder -o /dev/null %s | FileCheck %s
|
|
# This test ensures that the MIR parser parses the frame setup instruction flag.
|
|
|
|
--- |
|
|
|
|
define i32 @compute(i32 %a) {
|
|
body:
|
|
%c = mul i32 %a, 11
|
|
ret i32 %c
|
|
}
|
|
|
|
define i32 @foo(i32 %a) {
|
|
entry:
|
|
%b = call i32 @compute(i32 %a)
|
|
ret i32 %b
|
|
}
|
|
|
|
...
|
|
---
|
|
name: compute
|
|
body: |
|
|
bb.0.body:
|
|
%eax = IMUL32rri8 %edi, 11, implicit-def %eflags
|
|
RETQ %eax
|
|
...
|
|
---
|
|
name: foo
|
|
body: |
|
|
bb.0.entry:
|
|
; CHECK: frame-setup PUSH64r %rax
|
|
frame-setup PUSH64r %rax, implicit-def %rsp, implicit %rsp
|
|
CALL64pcrel32 @compute, csr_64, implicit %rsp, implicit %edi, implicit-def %rsp, implicit-def %eax
|
|
%rdx = POP64r implicit-def %rsp, implicit %rsp
|
|
RETQ %eax
|
|
...
|