public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbeulich at suse dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106741] suspicious %qE related warning when building gcc
Date: Fri, 26 Aug 2022 07:32:43 +0000	[thread overview]
Message-ID: <bug-106741-4-UZTZkPKULp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106741-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from jbeulich at suse dot com ---
If I'm reading the log right, it's stages 2 and 3 where the warnings appear,
while stage 1 (using gcc10) don't expose such a warning. Interestingly the
warnings do appear (once) when doing cross builds (again using gcc10) - do
stage1 builds have more warnings suppressed than (single-stage) cross builds?

There also was no such warning when building 12.1.0.

I guess this (in gcc/analyzer/analyzer.h) might matter:

/* Disable -Wformat-diag; we want to be able to use pp_printf
   for logging/dumping without complying with the rules for diagnostics.  */
#if __GNUC__ >= 10
#pragma GCC diagnostic ignored "-Wformat-diag"
#endif

This does neither suppress -Wformat= nor -Wformat-extra-args.

      parent reply	other threads:[~2022-08-26  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 15:27 [Bug analyzer/106741] New: " jbeulich at suse dot com
2022-08-25 17:08 ` [Bug analyzer/106741] " pinskia at gcc dot gnu.org
2022-08-25 17:13 ` pinskia at gcc dot gnu.org
2022-08-26  7:32 ` jbeulich at suse dot com [this message]

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-106741-4-UZTZkPKULp@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).