From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mingw GCC not recognising printf format "%I64u"
Date: Thu, 29 Jan 2009 09:00:46 -0600 [thread overview]
Message-ID: <4981C49E.5070207@codemonkey.ws> (raw)
In-Reply-To: <20090129135523.GA7441@shareable.org>
Jamie Lokier wrote:
> Anthony Liguori wrote:
>
>> Or we can just do
>>
>> #ifdef _WIN32
>> #define PRIu64 "%llu"
>> #endif
>>
>> or whatever the correct format is.
>>
>
> Qemu does that already!
>
I don't think so. mingw32 actuallt defines PRIu64 as "%I64u" even
though GCC doesn't like it. FWIW, the following seems to work for me:
/* Mingw has a broken PRIu64 */
#if defined(__MINGW32__)
#undef PRIu64
#define PRIu64 "Ld"
#endif
Regards,
Anthony Liguori
> It's just it defines the macro to "%I64u" because that's the WIN32 way
> of writing it...
>
> A quick Google reveals that "%llu" actually doesn't work on Mingw.
>
> (Though, if you were compiling on Cygwin (the Linux-like environment
> for Windows), you must use "%llu". But that also defines _WIN32... ho hum).
>
> -- Jamie
>
>
>
>> Regards,
>>
>> Anthony Liguori
>>
>>
>>> I won't blame it for not doing so, BeOS didn't have them either (but
>>> hey, it was out before C99...).
>>>
>>> François.
>>>
>>>
>>>
>>>
>>
>>
>
>
>
next prev parent reply other threads:[~2009-01-29 15:01 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 [this message]
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
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=4981C49E.5070207@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).