llvm-project/clang/test/Misc/serialized-diags-unknown-target.c

// RUN: rm -rf %t && mkdir %t
// RUN: not %clang_cc1 %s -triple blah-unknown-unknown -serialize-diagnostic-file %t/diag -o /dev/null 2>&1 | FileCheck %s

// CHECK: error: unknown target triple 'blah-unknown-unknown'{{$}}
[clang] Fix serialized diagnostics edge-cases The Clang frontend sometimes fails on the following assertion when launched with `-serialize-diagnostic-file <x>`: ``` Assertion failed: (BlockScope.empty() && CurAbbrevs.empty() && "Block imbalance"), function ~BitstreamWriter, file BitstreamWriter.h, line 125. ``` This was first noticed when passing an unknown command-line argument to `-cc1`. It turns out the `DiagnosticConsumer::finish()` function should be called as soon as processing of all source files ends, but there are some code paths where that doesn't happen: 1. when command line parsing fails in `cc1_main()`, 2. when `!Act.PrepareToExecute(*this)` or `!createTarget()` evaluate to `true` in `CompilerInstance::ExecuteAction` and the function returns early. This patch ensures `finish()` is called in all those code paths. Reviewed By: Bigcheese Differential Revision: https://reviews.llvm.org/D118150 2022-01-26 11:21:49 +01:00			`// RUN: rm -rf %t && mkdir %t`
			`// RUN: not %clang_cc1 %s -triple blah-unknown-unknown -serialize-diagnostic-file %t/diag -o /dev/null 2>&1 \| FileCheck %s`

[Driver] Drop incorrect hint from err_target_unknown_triple For an unknown target triple, the ", please use -triple or -arch" hint of the diagnostic is almost always wrong. For cc1, the error is due to a specified but unknown -triple. For driver, -triple and -arch are not driver options. 2023-05-01 18:22:49 -07:00			`// CHECK: error: unknown target triple 'blah-unknown-unknown'{{$}}`