Adds blacklist parsing behaviour for filtering results into four categories:
- Expected Protected: Things that are not in the blacklist and are protected.
- Unexpected Protected: Things that are in the blacklist and are protected.
- Expected Unprotected: Things that are in the blacklist and are unprotected.
- Unexpected Unprotected: Things that are not in the blacklist and are unprotected.
llvm-cfi-verify now can optionally be invoked with a second command line argument, which specifies the blacklist file that the binary was built with.
Current -fsanitize=cfi-vcall,cfi-icall statistics for chromium:
Expected Protected: 100375 (69.00%) Unexpected Protected: 12171 (8.37%) Expected Unprotected: 16207 (11.14%) Unexpected Unprotected (BAD): 16726 (11.50%)
Will this do what we expect when !LineInfo?