public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37768] bogus warnings on x86_64-mingw32 due to attribute((format(printf))) breakage
Date: Thu, 09 Oct 2008 07:05:00 -0000 [thread overview]
Message-ID: <20081009070401.12525.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37768-7665@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from mikpe at it dot uu dot se 2008-10-09 07:04 -------
> > The program below illustrates the issue. It declares a private C99-compliant
> > snprintf() implementation and invokes it with "%zu" and "%llx" formats. This
> > triggers the following bogus warnings on x86_64-pc-mingw32:
>
> Use gnu_printf for such an implementation.
Thanks. Using gnu_printf (new in 4.4) solves the issues I had.
--
mikpe at it dot uu dot se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37768
prev parent reply other threads:[~2008-10-09 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 9:31 [Bug c/37768] New: " mikpe at it dot uu dot se
2008-10-08 16:16 ` [Bug c/37768] " joseph at codesourcery dot com
2008-10-09 7:05 ` mikpe at it dot uu dot se [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=20081009070401.12525.qmail@sourceware.org \
--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).