-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Object: Don't error out on malformed bitcode files. #96848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,45 +1,75 @@ | ||
## Show that the archive library emits error messages when adding malformed | ||
## objects. | ||
## object files and skips symbol tables for "malformed" bitcode files, which | ||
## are assumed to be bitcode files generated by compilers from the future. | ||
|
||
# RUN: rm -rf %t.dir | ||
# RUN: split-file %s %t.dir | ||
# RUN: cd %t.dir | ||
|
||
## Malformed bitcode object is the first file member of archive if the symbol table is required. | ||
## Create a malformed bitcode object. | ||
# RUN: llvm-as input.ll -o input.bc | ||
# RUN: cp input.bc good.bc | ||
# RUN: %python -c "with open('input.bc', 'a') as f: f.truncate(10)" | ||
# RUN: not llvm-ar rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
|
||
## Malformed bitcode object is the last file member of archive if the symbol table is required. | ||
## Malformed bitcode objects either warn or error depending on the archive format | ||
## (see switch in getSymbolicFile). If the archive was created with a warning, | ||
## we want to check that the archive map is empty. llvm-nm will fail when it | ||
## tries to read the malformed bitcode file, but it's supposed to print the | ||
## archive map first, which in this case it won't because there won't be one. | ||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar rc bad.a good.bc input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
# RUN: llvm-ar --format=bsd rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=WARN1 | ||
# RUN: not llvm-nm --print-armap bad.a | count 0 | ||
# RUN: rm -rf bad.a | ||
# RUN: llvm-ar --format=gnu rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=WARN1 | ||
# RUN: not llvm-nm --print-armap bad.a | count 0 | ||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar --format=bigarchive rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar --format=coff rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar --format=darwin rc bad.a input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
|
||
## Malformed bitcode object is the last file member of archive and | ||
## the symbol table is required. In this case we check that the | ||
## symbol table contains entries for the good object only. | ||
# RUN: rm -rf bad.a | ||
# RUN: llvm-ar rc bad.a good.bc input.bc 2>&1 | FileCheck %s --check-prefix=WARN1 | ||
# RUN: not llvm-nm --print-armap bad.a | FileCheck %s --check-prefix=ARMAP | ||
|
||
## Malformed bitcode object if the symbol table is not required for big archive. | ||
## For big archives we print an error instead of a warning because the AIX linker | ||
## presumably requires the index. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @diggerlin, could you confirm that the big archive format does require the archive symbol index, please? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @EsmeYi / @hubert-reinterpretcast are either of you able to advise? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not familiar with XCOFF, but it presumably requires the index. ELF linkers like lld and mold have ignored the index completely (https://maskray.me/blog/2022-01-16-archives-and-start-lib). lld's wasm port has followed up, but other ports keep using the index. (I do want to help, but changing the other ports has a very low priority in my task list...) |
||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar --format=bigarchive rcS bad.a input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
# RUN: rm -rf bad.a | ||
# RUN: not llvm-ar --format=bigarchive rcS bad.a good.bc input.bc 2>&1 | FileCheck %s --check-prefix=ERR1 | ||
|
||
# ERR1: error: bad.a: 'input.bc': Invalid bitcode signature | ||
# WARN1: warning: 'input.bc': Invalid bitcode signature | ||
|
||
## Non-bitcode malformed file. | ||
# RUN: yaml2obj input.yaml -o input.o | ||
# RUN: not llvm-ar rc bad.a input.o 2>&1 | FileCheck %s --check-prefix=ERR2 | ||
|
||
# ERR2: error: bad.a: 'input.o': section header table goes past the end of the file: e_shoff = 0x9999 | ||
|
||
## Don't emit an error if the symbol table is not required for formats other than the big archive format. | ||
# RUN: llvm-ar --format=gnu rcS good.a input.o input.bc | ||
## Don't emit an error or warning if the symbol table is not required for formats other than the big archive format. | ||
# RUN: llvm-ar --format=gnu rcS good.a input.o input.bc 2>&1 | count 0 | ||
# RUN: llvm-ar t good.a | FileCheck %s --check-prefix=CONTENTS | ||
|
||
# CONTENTS: input.o | ||
# CONTENTS-NEXT: input.bc | ||
|
||
# ARMAP: Archive map | ||
# ARMAP-NEXT: foo in good.bc | ||
# ARMAP-EMPTY: | ||
|
||
#--- input.ll | ||
target datalayout = "e-m:w-i64:64-f80:128-n8:16:32:64-S128" | ||
target triple = "x86_64-pc-linux" | ||
|
||
@foo = global i32 1 | ||
|
||
#--- input.yaml | ||
--- !ELF | ||
FileHeader: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2>&1
and check the stderr as well?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we only want to test that there is no archive map. The test happens to use the functionality of llvm-nm. We don't particularly care whether (how) llvm-nm fails afterwards, because this is not a test of llvm-nm. We need to use
not
but that's only necessary to prevent the llvm-nm failure from causing a test failure.With
2>&1
we would need to test that the first line of llvm-nm output is something likeBut I don't think there's a way to use FileCheck to check that the first line of output matches a pattern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must admit, I thought a
CHECK-FIRST
directive was added to FileCheck, to allow that, but evidently not. If you did want to check that something is the first line though, I think you can do something like this:This works, because the
{{^}}
matches the start of the line, and since every line has a start, it matches specifically the first line. TheCHECK-SAME
then pins the thing it's checking to the previously-matched line, i.e. the first line.(I am ambivalent on whether you should do this for this specific case, but I think it may be worth a comment explaining why you're doing this llvm-nm invocation here either way)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a comment. That's an interesting trick, but it's probably not worth it here.