public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/94982] '-Wformat-diag' diagnostics building GCC
Date: Wed, 25 Nov 2020 22:01:58 +0000	[thread overview]
Message-ID: <bug-94982-4-T7PPN6C80p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94982-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94982

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:ca23341b28cd3af7985b83a6479107d9ea145a90

commit r11-5393-gca23341b28cd3af7985b83a6479107d9ea145a90
Author: Martin Sebor <msebor@redhat.com>
Date:   Wed Nov 25 14:05:01 2020 -0700

    Clean up -Wformat-diag warnings (PR bootstrap/97622, PR bootstrap/94982)

    gcc/c-family/ChangeLog:

            PR bootstrap/94982
            * c-attribs.c (handle_patchable_function_entry_attribute): Avoid
            -Wformat-diag.

    gcc/cp/ChangeLog:

            PR bootstrap/94982
            * constraint.cc (debug_argument_list): Avoid -Wformat-diag.
            * error.c (function_category): Same.
            (print_template_differences): Same.
            * logic.cc (debug): Same.
            * name-lookup.c (lookup_using_decl): Same.
            * parser.c (maybe_add_cast_fixit): Same.
            (cp_parser_template_introduction): Same.
            * typeck.c (access_failure_info::add_fixit_hint): Same.

    gcc/ChangeLog:

            PR bootstrap/97622
            PR bootstrap/94982
            * config/i386/i386-options.c (ix86_valid_target_attribute_inner_p):
            Avoid -Wformat-diag.
            * digraph.cc (struct test_edge): Same.
            * dumpfile.c (dump_loc): Same.
            (dump_context::begin_scope): Same.
            * edit-context.c (edited_file::print_diff): Same.
            (edited_file::print_diff_hunk): Same.
            * json.cc (object::print): Same.
            * lto-wrapper.c (merge_and_complain): Same.
            * reload.c (find_reloads): Same.
            * tree-diagnostic-path.cc (print_path_summary_as_text): Same.
            * ubsan.c (ubsan_type_descriptor): Same.

    gcc/jit/ChangeLog:

            PR bootstrap/94982
            * jit-recording.c (recording::function::dump_to_dot): Avoid
            -Wformat-diag.
            (recording::block::dump_to_dot): Same.

    gcc/testsuite/ChangeLog:

            PR bootstrap/94982
            * c-c++-common/patchable_function_entry-error-3.c: Adjust text
            of expected warning.

  parent reply	other threads:[~2020-11-25 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 10:46 [Bug other/94982] New: " tschwinge at gcc dot gnu.org
2020-05-07 14:54 ` [Bug other/94982] " msebor at gcc dot gnu.org
2020-11-25  1:10 ` msebor at gcc dot gnu.org
2020-11-25 22:01 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-25 22:07 ` msebor at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94982-4-T7PPN6C80p@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).