3 ;; The LLVM bitcode format allows for an optional wrapper header. This test
4 ;; shows that LLD can handle bitcode wrapped in this way, and also that an
5 ;; invalid offset in the wrapper header is handled cleanly.
8 ; RUN: split-file %s %t
9 ; RUN: llvm-as %t/ir.ll -o %t.bc
12 ; RUN: %python %t/wrap_bitcode.py %t.bc %t.o 0 0x14
13 ; RUN: ld.lld %t.o -o %t.elf
14 ; RUN: llvm-readelf -s %t.elf | FileCheck %s
16 ;; Padding between wrapper header and body:
17 ; RUN: %python %t/wrap_bitcode.py %t.bc %t.o 0x10 0x24
18 ; RUN: ld.lld %t.o -o %t.elf
19 ; RUN: llvm-readelf -s %t.elf | FileCheck %s
23 ;; Invalid offset past end of file:
24 ; RUN: %python %t/wrap_bitcode.py %t.bc %t2.o 0x10 0xffffffff
25 ; RUN: not ld.lld %t2.o -o %t2.elf 2>&1 | FileCheck %s --check-prefix=ERR1 -DFILE=%t2.o
27 ; ERR1: error: [[FILE]]: Invalid bitcode wrapper header
29 ;; Invalid offset within file:
30 ; RUN: %python %t/wrap_bitcode.py %t.bc %t3.o 0x10 0x14
31 ; RUN: not ld.lld %t3.o -o %t3.elf 2>&1 | FileCheck %s --check-prefix=ERR2 -DFILE=%t3.o
33 ; ERR2: error: [[FILE]]: file doesn't start with bitcode header
36 target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
37 target triple = "x86_64-unknown-linux-gnu"
39 @_start = global i32 0
42 ## Arguments are: input file, output file, padding size, offset value.
46 with open(sys.argv[1], 'rb') as input:
47 bitcode = input.read()
49 padding = int(sys.argv[3], 16) * b'\0'
50 offset = int(sys.argv[4], 16)
51 header = struct.pack('<IIIII', 0x0B17C0DE, 0, offset, len(bitcode), 0)
52 with open(sys.argv[2], 'wb') as output: