File: padding.test

package info (click to toggle)
llvm-toolchain-3.9 1%3A3.9.1-9
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 441,144 kB
  • ctags: 428,836
  • sloc: cpp: 2,546,577; ansic: 538,318; asm: 119,677; objc: 103,316; python: 102,148; sh: 27,847; pascal: 5,626; ml: 5,510; perl: 5,293; lisp: 4,801; makefile: 2,177; xml: 686; cs: 362; php: 212; csh: 117
file content (18 lines) | stat: -rw-r--r-- 656 bytes parent folder | download | duplicates (46)
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