diff options
| author | Dimitry Andric <dim@FreeBSD.org> | 2015-06-21 13:59:01 +0000 |
|---|---|---|
| committer | Dimitry Andric <dim@FreeBSD.org> | 2015-06-21 13:59:01 +0000 |
| commit | 3a0822f094b578157263e04114075ad7df81db41 (patch) | |
| tree | bc48361fe2cd1ca5f93ac01b38b183774468fc79 /test/Bitcode/padding.test | |
| parent | 85d8b2bbe386bcfe669575d05b61482d7be07e5d (diff) | |
Diffstat (limited to 'test/Bitcode/padding.test')
| -rw-r--r-- | test/Bitcode/padding.test | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/test/Bitcode/padding.test b/test/Bitcode/padding.test new file mode 100644 index 000000000000..63b2fec2b59e --- /dev/null +++ b/test/Bitcode/padding.test @@ -0,0 +1,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 |