From: Ankur Saini <arsenic.secondary@gmail.com>
To: Kris Andersen <kris.andersen@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: syslog: ISO C does not support the ‘%m’ gnu_printf format
Date: Tue, 25 Jan 2022 12:35:09 +0530 [thread overview]
Message-ID: <724C5503-0392-4397-91E8-171E6A3CC0AF@gmail.com> (raw)
In-Reply-To: <CABk8Po9W-oEs9+6BNtxRprmkg0b2HOhQ9PPTcTfP40rF_99hEA@mail.gmail.com>
> On 25-Jan-2022, at 9:38 AM, Kris Andersen via Gcc <gcc@gcc.gnu.org> wrote:
>
> The %m format specifier is a documented feature of syslog, but gcc gives a
> warning when -Wpedantic is used. Is this a bug?
>
> For example, the program:
>
> #include <syslog.h>
> int main(void)
> {
> syslog(LOG_ERR, "%m");
> return 0;
> }
>
> gives:
> warning: ISO C does not support the ‘%m’ gnu_printf format [-Wformat=]
I think, the compiler is correct by complaining about it when strict
warnings are enabled.
according to GNU documentation
(http://www.gnu.org/software/libc/manual/html_node/Other-Output-Conversions.html)
“ The ‘%m’ conversion is a GNU C Library extension “
>
> when compiled[1] with
> gcc -Wall -Wextra -Wpedantic -o test test.c
>
> The man page for syslog(3) states that %m is supported: "the two-character
> sequence %m will be replaced by the error message string strerror(errno)."
>
> Submitting a bug report for this feels like arguing that the answer in the
> back of the book is wrong (...rarely the right move). What am I missing
> here?
FWIW, A bug report requesting support for __format__ attribute for
syslog is already filed as bug 15338 (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15338 )
Thanks
- Ankur
prev parent reply other threads:[~2022-01-25 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 4:08 Kris Andersen
2022-01-25 7:05 ` Ankur Saini [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=724C5503-0392-4397-91E8-171E6A3CC0AF@gmail.com \
--to=arsenic.secondary@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=kris.andersen@gmail.com \
/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).