mono/linux-packaging-mono
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Imported Upstream version 5.18.0.161

Browse Source 
Former-commit-id: 4db48158d3a35497b8f118ab21b5f08ac3d86d98
This commit is contained in:
Xamarin Public Jenkins (auto-signing)
2018-10-19 08:34:24 +00:00
parent 37fbf886a3
commit e19d552987
28702 changed files with 3868076 additions and 803 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
external/llvm/test/tools/dsymutil/fat-binary-output.test vendored Normal file
View File

@@ -0,0 +1,30 @@
RUN: llvm-dsymutil -f -verbose -no-output %p/Inputs/fat-test.dylib -oso-prepend-path %p | FileCheck %s
This test doesn't produce any filesytstem output, we just look at the verbose
log output.
For each arch in the binary, check that we emit the right triple with the right
file and the right symbol inside it (each slice has a different symbol, so that
means that the logic is looking at the right file slice too).
After the link of each architecture, check that lipo is correctly invoked to
generate the fat output binary.
CHECK: triple: 'x86_64-apple-darwin'
CHECK: - filename: {{'?}}[[INPUTS_PATH:.*]]fat-test.o
CHECK: DW_AT_name{{.*}} "x86_64_var"
CHECK: triple: 'i386-apple-darwin'
CHECK: - filename: {{'?}}[[INPUTS_PATH]]fat-test.o
CHECK: DW_AT_name{{.*}} "i386_var"
CHECK: triple: 'x86_64h-apple-darwin'
CHECK: - filename: {{'?}}[[INPUTS_PATH]]fat-test.o
CHECK: DW_AT_name{{.*}} "x86_64h_var"
CHECK: Running lipo
CHECK-NEXT: lipo -create
CHECK-SAME [[TMP_PATH:.*?]]fat-test.dylib.tmp{{......}}.dwarf [[TMP_PATH]]fat-test.dylib.tmp{{......}}.dwarf [[TMP_PATH]]fat-test.dylib.tmp{{......}}.dwarf
CHECK-SAME: -segalign x86_64 20 -segalign i386 20 -segalign x86_64h 20
CHECK-SAME: -output [[INPUTS_PATH]]fat-test.dylib.dwarf