File: stack-object-invalid-name.mir

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-11
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,418,840 kB
  • sloc: cpp: 5,290,826; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,898; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,913; xml: 953; cs: 573; fortran: 539
file content (28 lines) | stat: -rw-r--r-- 709 bytes parent folder | download | duplicates (10) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 
# RUN: not llc -march=x86-64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
# This test ensures that the MIR parser reports an error when it encounters a
# stack object with a name that can't be associated with an alloca instruction.

--- |

  define i32 @test(i32 %a) {
  entry:
    %b = alloca i32
    store i32 %a, i32* %b
    %c = load i32, i32* %b
    ret i32 %c
  }

...
---
name:            test
frameInfo:
  maxAlignment:  4
stack:
  # CHECK: [[@LINE+1]]:20: alloca instruction named 'x' isn't defined in the function 'test'
  - { id: 0, name: x, offset: -12, size: 4, alignment: 4 }
body: |
  bb.0.entry:
    MOV32mr $rsp, 1, _, -4, _, $edi
    $eax = MOV32rm $rsp, 1, _, -4, _
    RETQ $eax
...