aprantl added a comment. In https://reviews.llvm.org/D38042#875303, @chandlerc wrote:
> But, the verifier itself will just "crash". It won't print a stack trace, but > I don't see why that's much better? And this flag is supposed to be a > developer option and not a user facing one, so I'm somewhat confused at what > the intent is here... No, it will report_fatal_error() instead of crashing the compiler later on. In any case, that is not my primary motivation: The intent is exactly what is illustrated by the testcase, stripping malformed debug info metadata produced by older, buggy versions of clang. The backstory to this is that historically the Verifier was very weak when it came to verifying debug info. To allow us to make the Verifier better (stricter), while still supporting importing of older .bc files produced by older compilers, we added a mechanism that strips all debug info metadata if the verification of the debug info failed, but the bitcode is otherwise correct. https://reviews.llvm.org/D38042 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
