xref: /aosp_15_r20/external/llvm/test/tools/dsymutil/ARM/fat-arch-name.test (revision 9880d6810fe72a1726cb53787c6711e909410d58)
1*9880d681SAndroid Build Coastguard Worker# REQUIRES: object-emission
2*9880d681SAndroid Build Coastguard Worker# RUN: llvm-dsymutil -no-output %p/../Inputs/fat-test.arm.dylib -o %t.dSYM -verbose 2>&1 | FileCheck %s
3*9880d681SAndroid Build Coastguard Worker
4*9880d681SAndroid Build Coastguard Worker# We detect thumb triples from the binaries, because those are the only ones
5*9880d681SAndroid Build Coastguard Worker# that are guaranteed to be able to generate a Target instance (for example
6*9880d681SAndroid Build Coastguard Worker# we would detect armv7m-apple-darwin as non-thumb triple, but you can't
7*9880d681SAndroid Build Coastguard Worker# instantiate a Target from that). In the user-visible architecture names, and
8*9880d681SAndroid Build Coastguard Worker# in the lipo invocation, we need to rewrite the thumb arch names to the arm
9*9880d681SAndroid Build Coastguard Worker# ones.
10*9880d681SAndroid Build Coastguard Worker
11*9880d681SAndroid Build Coastguard Worker# CHECK: warning: no debug symbols in executable (-arch armv7)
12*9880d681SAndroid Build Coastguard Worker
13*9880d681SAndroid Build Coastguard Worker# CHECK: warning: no debug symbols in executable (-arch armv7s)
14*9880d681SAndroid Build Coastguard Worker
15*9880d681SAndroid Build Coastguard Worker# CHECK: warning: no debug symbols in executable (-arch arm64)
16*9880d681SAndroid Build Coastguard Worker
17*9880d681SAndroid Build Coastguard Worker# CHECK: Running lipo
18*9880d681SAndroid Build Coastguard Worker# CHECK-NEXT: lipo -create
19*9880d681SAndroid Build Coastguard Worker# CHECK-SAME: -segalign armv7
20*9880d681SAndroid Build Coastguard Worker# CHECK-SAME: -segalign armv7s
21*9880d681SAndroid Build Coastguard Worker# CHECK-SAME: -segalign arm64
22