llc crash when exec 'llc -mtriple=sparcel'

[cpython-java]

description

when i use 'llc' to translate an IR, crash happened. I don't know whether it's a bug of 'llc' and want to be sure about it.

thank you for your help!

bug ir

define i32 @main() {
  
  br label %2

2: 
  %A = alloca i64, align 16
  ret i32 0
}

cmd

llc -mtriple=sparcel test.ll

crash info

https://godbolt.org/z/hEafj9887

[asl]

The error is:

LLVM ERROR: Function "main": over-aligned dynamic alloca not supported.

So, this is simply not something supported by old Sparc backend.

[llvmbot]

@llvm/issue-subscribers-bug

Author: None (cpython-java)

Details

# description when i use 'llc' to translate an IR, crash happened. I don't know whether it's a bug of 'llc' and want to be sure about it.

thank you for your help!

bug ir

define i32 @<!-- -->main() {
  
  br label %2

2: 
  %A = alloca i64, align 16
  ret i32 0
}

cmd

llc -mtriple=sparcel test.ll

crash info

https://godbolt.org/z/hEafj9887

[cpython-java]

The error is:

LLVM ERROR: Function "main": over-aligned dynamic alloca not supported.

So, this is simply not something supported by old Sparc backend.

So it's a problem about align. But why the following code has no problem??? Thank you for your help!!!!!

define i32 @main() {
  %A = alloca i64, align 16
  ret i32 0
}

the difference between two IR is only whether instruction 'br' exists.

[asl]

First one is a dynamic alloca requiring stack realignment.

[cpython-java]

First one is a dynamic alloca requiring stack realignment.

If the syntax is not supported, should the llc alert the user with an error instead of crashing?

[brad0]

@koachan

[koachan]

From a quick look it seems that this also affects all the other 32-bit targets...
But yeah lemme see what I can do here.