public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/28492] -Wmissing-format-attribute causes warning for vsnprintf()
Date: Tue, 17 Apr 2012 22:19:00 -0000 [thread overview]
Message-ID: <bug-28492-4-WqyyKUxWcR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28492-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28492
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-04-17
CC| |manu at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-17 22:17:01 UTC ---
OK, I see that the warning is misleading, because it points to the call of
vsnprintf instead of pointing to vsnprintf_one.
ttest.c: In function ‘vsnprintf_one’:
ttest.c:826:5: warning: function might be possible candidate for ‘gnu_printf’
format attribute [-Wmissing-format-attribute]
vsnprintf(self, 2, "%c", arglist);
^
next parent reply other threads:[~2012-04-17 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28492-4@http.gcc.gnu.org/bugzilla/>
2012-04-17 22:19 ` manu at gcc dot gnu.org [this message]
2024-01-09 13:23 ` [Bug c/28492] -Wmissing-format-attribute points to vsnprintf() or related functions instead of the function that needs the attribute added manu at gcc dot gnu.org
2024-06-21 22:50 ` [Bug c/28492] -Wsuggest-attribute=format " egallager at gcc dot gnu.org
2006-07-26 13:39 [Bug c/28492] New: -Wmissing-format-attribute causes warning for vsnprintf() llundin at eso dot org
2007-01-13 18:40 ` [Bug c/28492] " h dot b dot furuseth at usit dot uio dot no
2010-04-04 15:08 ` bernard dot van dot duijnen at oracle dot com
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-28492-4-WqyyKUxWcR@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).