1; This isn't really an assembly file, its just here to run the test. 2 3; This test just makes sure that llvm-ar can extract bytecode members 4; from various style archives. 5 6; REQUIRES: shell 7 8; RUN: cd %T 9 10; RUN: rm -f very_long_bytecode_file_name.bc 11; RUN: llvm-ar p %p/Inputs/GNU.a very_long_bytecode_file_name.bc | \ 12; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc - 13; RUN: llvm-ar x %p/Inputs/GNU.a very_long_bytecode_file_name.bc 14; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc \ 15; RUN: very_long_bytecode_file_name.bc 16 17; RUN: rm -f very_long_bytecode_file_name.bc 18; RUN: llvm-ar p %p/Inputs/MacOSX.a very_long_bytecode_file_name.bc | \ 19; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc - 20; RUN: llvm-ar x %p/Inputs/MacOSX.a very_long_bytecode_file_name.bc 21; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc \ 22; RUN: very_long_bytecode_file_name.bc 23 24; RUN: rm -f very_long_bytecode_file_name.bc 25; RUN: llvm-ar p %p/Inputs/SVR4.a very_long_bytecode_file_name.bc | \ 26; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc - 27; RUN: llvm-ar x %p/Inputs/SVR4.a very_long_bytecode_file_name.bc 28; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc \ 29; RUN: very_long_bytecode_file_name.bc 30 31; RUN: rm -f very_long_bytecode_file_name.bc 32; RUN: llvm-ar p %p/Inputs/xpg4.a very_long_bytecode_file_name.bc |\ 33; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc - 34; RUN: llvm-ar x %p/Inputs/xpg4.a very_long_bytecode_file_name.bc 35; RUN: cmp -s %p/Inputs/very_long_bytecode_file_name.bc \ 36; RUN: very_long_bytecode_file_name.bc 37 38 39; Test that the 'o' option is working by extracting a file, putting it in o 40; new archive and checking that date. 41; RUN: rm -f very_long_bytecode_file_name.bc 42; RUN: llvm-ar xo %p/Inputs/GNU.a very_long_bytecode_file_name.bc 43; RUN: llvm-ar rc %t.a very_long_bytecode_file_name.bc 44; RUN: env TZ=GMT llvm-ar tv %t.a | FileCheck %s 45 46CHECK: 1465 Nov 19 03:01 2004 very_long_bytecode_file_name.bc 47