From 90374df15ddc58d823ca42326a76f58e748f20eb Mon Sep 17 00:00:00 2001 From: Balazs Benics Date: Fri, 10 Jun 2022 14:47:23 +0200 Subject: [PATCH] [analyzer] Fix buildbots after introducing a new frontend warning It seems like I should have ran the `check-clang` target after introducing a new warning diagnostic entry. My bad. I'll run it next time; `check-clang-analysis` was not enough. Here is a link to the broken bot: http://45.33.8.238/linux/78236/step_7.txt This commit should fix this. Differential Revision: https://reviews.llvm.org/D126067 --- clang/test/Misc/warning-flags.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/clang/test/Misc/warning-flags.c b/clang/test/Misc/warning-flags.c index ac9a1f9..6da9e42 100644 --- a/clang/test/Misc/warning-flags.c +++ b/clang/test/Misc/warning-flags.c @@ -18,7 +18,7 @@ This test serves two purposes: The list of warnings below should NEVER grow. It should gradually shrink to 0. -CHECK: Warnings without flags (66): +CHECK: Warnings without flags (67): CHECK-NEXT: ext_expected_semi_decl_list CHECK-NEXT: ext_explicit_specialization_storage_class @@ -33,6 +33,7 @@ CHECK-NEXT: pp_invalid_string_literal CHECK-NEXT: pp_out_of_date_dependency CHECK-NEXT: pp_poisoning_existing_macro CHECK-NEXT: warn_accessor_property_type_mismatch +CHECK-NEXT: warn_analyzer_deprecated_option CHECK-NEXT: warn_arcmt_nsalloc_realloc CHECK-NEXT: warn_asm_label_on_auto_decl CHECK-NEXT: warn_c_kext -- 2.7.4