diff options
| author | Justin Bogner <mail@justinbogner.com> | 2014-10-20 21:02:05 +0000 |
|---|---|---|
| committer | Justin Bogner <mail@justinbogner.com> | 2014-10-20 21:02:05 +0000 |
| commit | e1a33d1e4c925ae4cfe36df13475e56762780360 (patch) | |
| tree | b272a85f211c8acbdf3f03ca29802420f4b9fff7 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 204607bc90b6ff4aaff96a078efa50486babb393 (diff) | |
| download | llvm-e1a33d1e4c925ae4cfe36df13475e56762780360.zip llvm-e1a33d1e4c925ae4cfe36df13475e56762780360.tar.gz llvm-e1a33d1e4c925ae4cfe36df13475e56762780360.tar.bz2 | |
Driver: Make FailingCommand mandatory for generateCompilationDiagnostics
We currently use a null FailingCommand when generating crash reports
as an indication that the cause is FORCE_CLANG_DIAGNOSTICS_CRASH, the
environment variable that exists to test crash dumps. This means that
our tests don't actually cover real crashes at all, and adds a more
complicated code path that's only used in the tests.
Instead, we can have the driver synthesize that every command failed
and just call generateCompilationDiagnostics normally.
llvm-svn: 220234
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions