public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105626] New: -Wformat should accept u8"" strings Date: Tue, 17 May 2022 12:13:41 +0000 [thread overview] Message-ID: <bug-105626-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105626 Bug ID: 105626 Summary: -Wformat should accept u8"" strings Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: drepper.fsp+rhbz at gmail dot com Target Milestone: --- The discussion about this topic on gcc@ (https://gcc.gnu.org/pipermail/gcc/2022-May/238673.html) ended with the conclusion that gcc should not disregard the cast in code like this: #include <stdio.h> int main() { printf((const char*) u8"test %d\n", 1); return 0; } With -Wformat this code produces with gcc 12: t.cc: In function ‘int main()’: t.cc:5:24: warning: format string is not an array of type ‘char’ [-Wformat=] 5 | printf((const char*) u8"test %d\n", 1); | ^~~~~~~~~~~~~ Since a) there are no I/O functions for u8 strings in C++20 b) using u8 strings is necessary in reliable code c) it is safe to perform the analysis -Wformat does on u8 strings I suggest that u8 strings are allowed when testing for -Wformat.
next reply other threads:[~2022-05-17 12:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 12:13 drepper.fsp+rhbz at gmail dot com [this message] 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 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@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: linkBe 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).