[patch] C++ FE warning control cleanup

[Lee Millward <lee dot millward at gmail dot com>]

Hi,

This patch adjusts calls to warning() in the C++ front end to not use
0 but instead use the appropriate OPT_W values, there was some other
calls which I didn't change as I wasn't totally sure of the right
value to use in it's place so this patch addresses the more obvious
occurrences.

Bootstrapped successfully on i686-pc-linux-gnu, is a regression test
required for patches of this nature?

2006-01-28  Lee Millward <lee.millward@gmail.com>

       *typeck.c (string_conv_p, build_array_ref):
       pass the appropriate OPT_Wxxxx warning flag when
       calling warning() instead of passing 0.
       (cxx_mark_addressable, check_return_expr): Likewise.

       *init.c (perform_member_init): Likewise.
       (sort_mem_initializers, emit_mem_initializers): Likewise.

       *class.c (check_bases, check_field_decl): Likewise.
       (check_field_decls, layout_empty_base): Likewise.
       (build_base_field, layout_virtual_bases): Likewise.
       (warn_about_ambiguous_bases, layout_class_type): Likewise.

       *decl.c (pop_label, poplevel, duplicate_decls): Likewise.
       (grok_op_properties, start_preparsed_function): Likewise.
       (finish_function): Likewise.

       *method.c (lazily_declare_fn): Likewise.
       *.cvt.c (convert_to_void): Likewise.
       *mangle.c (finish_mangling): Likewise
       *name-lookup.c (pushdecl_maybe_friend): Likewise.

       *parser.c (p_parser_warn_min_max): Likewise.
       (cp_parser_cast_expression): Likewise.

Attachment: warnings_patch.txt.tar.gz
Description: GNU Zip compressed data