File: padding.test

package info (click to toggle)
llvm-toolchain-21 1%3A21.1.7-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,245,064 kB
  • sloc: cpp: 7,619,731; ansic: 1,434,018; asm: 1,058,748; python: 252,740; f90: 94,671; objc: 70,685; lisp: 42,813; pascal: 18,401; sh: 8,601; ml: 5,111; perl: 4,720; makefile: 3,676; awk: 3,523; javascript: 2,409; xml: 892; fortran: 770
file content (18 lines) | stat: -rw-r--r-- 656 bytes parent folder | download | duplicates (37) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
 
Test that both llvm-dis (uses a data streamer) and opt (no data streamer)
handle a .bc file with any padding.

A file padded with '\n' can be produced under a peculiar situation:

* A .bc is produced os OS X, but without a darwin triple, so it has no
  wrapper.
* It is included in a .a archive
* ranlib is ran on that archive. It will pad the members to make them multiple
  of 8 bytes.

and there is no reason to not handle the general case.

RUN: llvm-dis -disable-output %p/Inputs/padding.bc
RUN: opt -disable-output %p/Inputs/padding.bc

RUN: llvm-dis -disable-output %p/Inputs/padding-garbage.bc
RUN: opt -disable-output %p/Inputs/padding-garbage.bc