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 c/97100] -Wformat checks all arms of _Generic leading to irrelevant type expectation warnings
Date: Sat, 05 Aug 2023 08:40:14 +0000	[thread overview]
Message-ID: <bug-97100-4-m1pDlpfW2I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97100-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:54be338589ea93ad4ff53d22adde476a0582537b

commit r14-3004-g54be338589ea93ad4ff53d22adde476a0582537b
Author: Martin Uecker <uecker@tugraz.at>
Date:   Fri Aug 4 07:48:21 2023 +0200

    c: _Generic should not warn in non-active branches
[PR68193,PR97100,PR110703]

    To avoid false diagnostics, use c_inhibit_evaluation_warnings when
    a generic association is known to not match during parsing.  We may
    still generate false positives if the default branch comes earler than
    a specific association that matches.

    PR c/68193
    PR c/97100
    PR c/110703

    gcc/c/:
            * c-parser.cc (c_parser_generic_selection): Inhibit evaluation
            warnings branches that are known not be taken during parsing.

    gcc/testsuite/ChangeLog:
            * gcc.dg/pr68193.c: New test.

  parent reply	other threads:[~2023-08-05  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  0:56 [Bug c/97100] New: " sherzberg+gcc at freeshell dot org
2023-07-17 12:11 ` [Bug c/97100] " Hi-Angel at yandex dot ru
2023-08-04  6:06 ` muecker at gwdg dot de
2023-08-05  8:40 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-03 19:26 ` uecker at gcc dot gnu.org
2024-04-16  3:07 ` alx at kernel dot org
2024-04-16  3:08 ` alx at kernel dot org
2024-04-16  5:35 ` uecker at gcc dot gnu.org
2024-04-16  5:58 ` Hi-Angel at yandex dot ru
2024-04-16  6:03 ` uecker at gcc dot gnu.org
2024-04-16  6:27 ` Hi-Angel at yandex dot ru
2024-04-16  7:02 ` muecker at gwdg dot de
2024-04-16  7:33 ` Hi-Angel at yandex dot ru
2024-04-16  8:23 ` muecker at gwdg dot de
2024-04-16  9:55 ` alx at kernel dot 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-97100-4-m1pDlpfW2I@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).