Similar to 806761a762
-mtriple= specifies the full target triple while -march= merely sets the
architecture part of the default target triple (e.g. Windows, macOS),
leaving a target triple which may not make sense.
Therefore, -march= is error-prone and not recommended for tests without
a target triple. The issue has been benign as we recognize
bpf*-apple-darwin as ELF instead of rejecting it outrightly.
13 lines
446 B
LLVM
13 lines
446 B
LLVM
; RUN: not llc -mtriple=bpf -mcpu=v1 < %s 2> %t1
|
|
; RUN: FileCheck %s < %t1
|
|
; CHECK: error: <unknown>:0:0: in function foo i32 (i32, i32, i32): {{t10|0x[0-f]+}}: i64 = GlobalAddress<ptr @bar> 0 too many arguments
|
|
|
|
; Function Attrs: nounwind uwtable
|
|
define i32 @foo(i32 %a, i32 %b, i32 %c) #0 {
|
|
entry:
|
|
%call = tail call i32 @bar(i32 %a, i32 %b, i32 %c, i32 1, i32 2, i32 3) #3
|
|
ret i32 %call
|
|
}
|
|
|
|
declare i32 @bar(i32, i32, i32, i32, i32, i32) #1
|