Author: Balazs Benics Date: 2022-06-10T14:47:23+02:00 New Revision: 90374df15ddc58d823ca42326a76f58e748f20eb
URL: https://github.com/llvm/llvm-project/commit/90374df15ddc58d823ca42326a76f58e748f20eb DIFF: https://github.com/llvm/llvm-project/commit/90374df15ddc58d823ca42326a76f58e748f20eb.diff LOG: [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 Added: Modified: clang/test/Misc/warning-flags.c Removed: ################################################################################ diff --git a/clang/test/Misc/warning-flags.c b/clang/test/Misc/warning-flags.c index ac9a1f9f010c2..6da9e423d94fe 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 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
