From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Mingw GCC not recognising printf format "%I64u"
Date: Thu, 29 Jan 2009 14:56:23 -0600 [thread overview]
Message-ID: <498217F7.80004@codemonkey.ws> (raw)
In-Reply-To: <glt4fq$72a$1@ger.gmane.org>
Consul wrote:
> Anthony Liguori wrote:
>> Okay, I wrote a small program that included inttypes.h. PRIu64 was
>> defined as I64u.
>
> This bug should be fixed in GCC-4.4.0 (and backported to 3.4.2 MinGW's
> stable) However the latest version ported to MinGW is still 4.3.0.
> Mind you I64u in the format line still gives the correct result, only
> this annoying warning is the problem. Other suggested format options
> silenced the warning, but also truncated the result :(
Okay, then we can just ignore it for now.
Regards,
Anthony Liguori
> #include<stdio.h>
> #include<inttypes.h>
> //#define PRIu64 "I64u"
> int main() {
> unsigned __int64 x = 1122334455667788LL;
> printf("Number: %"PRIu64"\n", x);
> return 0;
> }
>
>
>
prev parent reply other threads:[~2009-01-29 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 19:43 [Qemu-devel] [PATCH] Silence half of warnings in MinGW Consul
2009-01-28 21:50 ` Anthony Liguori
2009-01-29 6:21 ` [Qemu-devel] Mingw GCC not recognising printf format "%I64u" Jamie Lokier
2009-01-29 6:28 ` Jamie Lokier
2009-01-29 7:42 ` François Revol
2009-01-29 13:36 ` Anthony Liguori
2009-01-29 13:55 ` Jamie Lokier
2009-01-29 15:00 ` Anthony Liguori
2009-01-29 18:34 ` [Qemu-devel] " Consul
2009-01-29 18:42 ` [Qemu-devel] " Jamie Lokier
2009-01-29 19:50 ` Anthony Liguori
2009-01-29 20:44 ` [Qemu-devel] " Consul
2009-01-29 20:56 ` Anthony Liguori [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=498217F7.80004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).