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++/105626] -Wformat should accept u8"" strings
Date: Tue, 05 Jul 2022 21:35:35 +0000	[thread overview]
Message-ID: <bug-105626-4-oU9rtpRu1H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105626-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:543828e79bfa63ef26b11a2c9ea81fd7905f33aa

commit r13-1511-g543828e79bfa63ef26b11a2c9ea81fd7905f33aa
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Jul 5 14:22:26 2022 -0400

    c-family: Prevent -Wformat warnings with u8 strings [PR105626]

    The <https://gcc.gnu.org/pipermail/gcc/2022-May/238679.html> thread
    seems to have concluded that -Wformat shouldn't warn about

      printf((const char*) u8"test %d\n", 1);

    saying "format string is not an array of type 'char'".  This code
    is not an aliasing violation, and there are no I/O functions for u8
    strings, so the const char * cast is OK and shouldn't be disregarded.

            PR c++/105626

    gcc/c-family/ChangeLog:

            * c-format.cc (check_format_arg): Don't emit -Wformat warnings with
            u8 strings.

    gcc/testsuite/ChangeLog:

            * g++.dg/warn/Wformat-char8_t-1.C: New test.

  parent reply	other threads:[~2022-07-05 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 12:13 [Bug c++/105626] New: " drepper.fsp+rhbz at gmail dot com
2022-05-17 13:10 ` [Bug c++/105626] " mpolacek at gcc dot gnu.org
2022-07-04 20:38 ` drepper.fsp+rhbz at gmail dot com
2022-07-05 16:23 ` mpolacek at gcc dot gnu.org
2022-07-05 21:35 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-05 21:39 ` mpolacek at gcc dot gnu.org
2022-07-06  4:42 ` drepper.fsp+rhbz at gmail dot com
2022-07-06 12:53 ` cvs-commit 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-105626-4-oU9rtpRu1H@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).