maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Misc/warning-flags.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

95 lines
3.8 KiB
C
Raw Normal View History

Promote warn_unknown_analyzer_checker to an error. Addresses <rdar://problem/10987863>. llvm-svn: 160706
2012-07-25 15:12:13 +08:00
RUN: diagtool list-warnings > %t 2>&1
RUN: FileCheck --input-file=%t %s
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
This test serves two purposes:
(1) It documents all existing warnings that currently have no associated -W flag,
and ensures that the list never grows.
Remove trailing spaces llvm-svn: 194498
2013-11-13 02:07:35 +08:00
Fix grammar in comment. NFC llvm-svn: 302443
2017-05-09 01:06:17 +08:00
If you take an existing warning and add a flag, this test will fail.
To fix this test, simply remove that warning from the list below.
Remove trailing spaces llvm-svn: 194498
2013-11-13 02:07:35 +08:00
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
(2) It prevents us adding new warnings to Clang that have no -W flag. All
new warnings should have -W flags.
Remove trailing spaces llvm-svn: 194498
2013-11-13 02:07:35 +08:00
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
If you add a new warning without a flag, this test will fail. To fix
this test, simply add a warning group to that warning.
Remove trailing spaces llvm-svn: 194498
2013-11-13 02:07:35 +08:00
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
The list of warnings below should NEVER grow. It should gradually shrink to 0.
[Driver] Add disabled-by-default -Wuse-ld-path for the deprecation warning for -fuse-ld=/abs/path The warning is currently not under a -W option, so it cannot be suppressed. This is annoying for the widespread build system Bazel when specifying the path to gold https://github.com/bazelbuild/bazel/commit/cdd0c3cdba270115940e8ca5ec8104cbcd694671 I have notified them about using --ld-path= forwards https://github.com/bazelbuild/bazel/pull/8580#issuecomment-694321543 but we have to give some transitional period. Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87837
2020-09-20 06:49:44 +08:00
CHECK: Warnings without flags (68):
Create a warning flag for 'warn_conv_*_not_used' These warnings are grouped under '-Wclass-conversion' to be compatiable with GCC 9. Differential Revision: https://reviews.llvm.org/D78442
2020-06-10 20:55:42 +08:00
Fix horrible regression in control of warnings caused by introduction of -Wpedantic. While -Wpedantic was reasonable, -Wno-pedantic would turn off a bunch of warnings that are on by default. This counters the intention of this warning flag. To fix this, -Wpedantic now includes extentions that are not on by default. The remaining warnings will manifest anyway, and won't accidentally get turned off by -Wno-pedantic. Fixes <rdar://problem/12076105> llvm-svn: 161695
2012-08-11 04:50:00 +08:00
CHECK-NEXT: ext_expected_semi_decl_list
CHECK-NEXT: ext_explicit_specialization_storage_class
CHECK-NEXT: ext_missing_declspec
CHECK-NEXT: ext_missing_whitespace_after_macro_name
CHECK-NEXT: ext_new_paren_array_nonconst
CHECK-NEXT: ext_plain_complex
CHECK-NEXT: ext_template_arg_extra_parens
CHECK-NEXT: ext_typecheck_cond_incompatible_operands
CHECK-NEXT: ext_typecheck_ordered_comparison_of_pointer_integer
CHECK-NEXT: ext_using_undefined_std
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
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
ARCMT/GC-check-warn-nsalloc.m: don't provide a diag group This diagnostic is now controlled solely by -no-ns-alloc-error thus matching the original intended behaviour. llvm-svn: 209184
2014-05-20 07:48:49 +08:00
CHECK-NEXT: warn_arcmt_nsalloc_realloc
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_asm_label_on_auto_decl
CHECK-NEXT: warn_c_kext
CHECK-NEXT: warn_call_wrong_number_of_arguments
CHECK-NEXT: warn_case_empty_range
CHECK-NEXT: warn_char_constant_too_large
CHECK-NEXT: warn_collection_expr_type
CHECK-NEXT: warn_conflicting_variadic
CHECK-NEXT: warn_delete_array_type
CHECK-NEXT: warn_double_const_requires_fp64
CHECK-NEXT: warn_drv_assuming_mfloat_abi_is
CHECK-NEXT: warn_drv_clang_unsupported
CHECK-NEXT: warn_drv_pch_not_first_include
CHECK-NEXT: warn_dup_category_def
CHECK-NEXT: warn_enum_value_overflow
Fix horrible regression in control of warnings caused by introduction of -Wpedantic. While -Wpedantic was reasonable, -Wno-pedantic would turn off a bunch of warnings that are on by default. This counters the intention of this warning flag. To fix this, -Wpedantic now includes extentions that are not on by default. The remaining warnings will manifest anyway, and won't accidentally get turned off by -Wno-pedantic. Fixes <rdar://problem/12076105> llvm-svn: 161695
2012-08-11 04:50:00 +08:00
CHECK-NEXT: warn_expected_qualified_after_typename
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_extraneous_char_constant
Fix test/Misc/warning-flags.c after 5c03beefa720bddb3e3f53c595a76bce7ad50f37
2020-04-28 01:18:39 +08:00
CHECK-NEXT: warn_fe_backend_unsupported
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_fe_cc_log_diagnostics_failure
CHECK-NEXT: warn_fe_cc_print_header_failure
CHECK-NEXT: warn_fe_macro_contains_embedded_newline
CHECK-NEXT: warn_ignoring_ftabstop_value
CHECK-NEXT: warn_implements_nscopying
CHECK-NEXT: warn_incompatible_qualified_id
CHECK-NEXT: warn_invalid_asm_cast_lvalue
CHECK-NEXT: warn_maynot_respond
CHECK-NEXT: warn_method_param_redefinition
CHECK-NEXT: warn_missing_case_for_condition
Fix horrible regression in control of warnings caused by introduction of -Wpedantic. While -Wpedantic was reasonable, -Wno-pedantic would turn off a bunch of warnings that are on by default. This counters the intention of this warning flag. To fix this, -Wpedantic now includes extentions that are not on by default. The remaining warnings will manifest anyway, and won't accidentally get turned off by -Wno-pedantic. Fixes <rdar://problem/12076105> llvm-svn: 161695
2012-08-11 04:50:00 +08:00
CHECK-NEXT: warn_missing_dependent_template_keyword
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_missing_whitespace_after_macro_name
ARCMigrate: Introduce proper diagnostics for TransformActions This starts to switch ARCMT to use proper diagnostic messages. The old use was based on incorrect example code from the documentation. The logic of the previous report() functions has been retained to support any external consumers that might be intercepting diagnostic messages through the old interface. Note that the change in test/Misc/warning-flags.c isn't a new warning without a flag, rather one that was previously invisible to the test. Adding a flag might be a good idea though. llvm-svn: 200124
2014-01-26 13:07:32 +08:00
CHECK-NEXT: warn_mt_message
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_no_constructor_for_refconst
CHECK-NEXT: warn_not_compound_assign
CHECK-NEXT: warn_objc_property_copy_missing_on_block
CHECK-NEXT: warn_objc_protocol_qualifier_missing_id
CHECK-NEXT: warn_on_superclass_use
Use %select to merge similar diagnostics. NFC llvm-svn: 253119
2015-11-14 10:09:55 +08:00
CHECK-NEXT: warn_pp_convert_to_positive
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_pp_expr_overflow
CHECK-NEXT: warn_pp_line_decimal
Fix typos in clang Found via codespell -q 3 -I ../clang-whitelist.txt Where whitelist consists of: archtype cas classs checkk compres definit frome iff inteval ith lod methode nd optin ot pres statics te thru Patch by luzpaz! (This is a subset of D44188 that applies cleanly with a few files that have dubious fixes reverted.) Differential revision: https://reviews.llvm.org/D44188 llvm-svn: 329399
2018-04-06 23:14:32 +08:00
CHECK-NEXT: warn_pragma_pack_pop_identifier_and_alignment
Add diagtool-based test where we enforce that no additional warnings can be added to Clang without a -W flag. llvm-svn: 137369
2011-08-12 06:06:55 +08:00
CHECK-NEXT: warn_pragma_pack_show
CHECK-NEXT: warn_property_getter_owning_mismatch
CHECK-NEXT: warn_register_objc_catch_parm
CHECK-NEXT: warn_related_result_type_compatibility_class
CHECK-NEXT: warn_related_result_type_compatibility_protocol
CHECK-NEXT: warn_template_export_unsupported
CHECK-NEXT: warn_template_spec_extra_headers
CHECK-NEXT: warn_tentative_incomplete_array
CHECK-NEXT: warn_typecheck_function_qualifiers
CHECK-NEXT: warn_undef_interface
CHECK-NEXT: warn_undef_interface_suggest
CHECK-NEXT: warn_undef_protocolref
CHECK-NEXT: warn_weak_identifier_undeclared
CHECK-NEXT: warn_weak_import
Re-apply r159875 with fixes. - Split pedantic driver flag test into separate test file, and XFAIL on cygwin,mingw32 - Fix bug in tablegen logic where a missing '{' caused errors to be included in -Wpedantic. llvm-svn: 159892
2012-07-07 13:53:30 +08:00
Add diagnostics for comma at end of enum and for extra semicolon at namespace scope to -Wc++11-extensions. Move extra semicolon after member function definition diagnostic out of -pedantic, since C++ allows a single semicolon there. Keep it in -Wextra-semi, though, since it's still questionable. llvm-svn: 160618
2012-07-23 13:45:25 +08:00
The list of warnings in -Wpedantic should NEVER grow.
Enhance 'diagtool list-warnings' to report number of diagnostics covered directly under -Wpedantic, and enhance warning-flags.c test to test that this set does not grow. llvm-svn: 159893
2012-07-07 14:30:31 +08:00
PR44406: Follow behavior of array bound constant folding in more recent versions of GCC. Old GCC used to aggressively fold VLAs to constant-bound arrays at block scope in GNU mode. That's non-conforming, and more modern versions of GCC only do this at file scope. Update Clang to do the same. Also promote the warning for this from off-by-default to on-by-default in all cases; more recent versions of GCC likewise warn on this by default. This is still slightly more permissive than GCC, as pointed out in PR44406, as we still fold VLAs to constant arrays in structs, but that seems justifiable given that we don't support VLA-in-struct (and don't intend to ever support it), but GCC does. Differential Revision: https://reviews.llvm.org/D89523
2020-10-16 10:32:15 +08:00
CHECK: Number in -Wpedantic (not covered by other -W flags): 26