From: Markus Armbruster <armbru@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] mingw32 compile fixes
Date: Mon, 17 May 2010 10:37:51 +0200 [thread overview]
Message-ID: <m3vdamvs80.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <AANLkTinYfoAXnNqvvBls6IEA3beM4M0AeREXibVb_2tP@mail.gmail.com> (Blue Swirl's message of "Sun, 16 May 2010 11:24:59 +0300")
Blue Swirl <blauwirbel@gmail.com> writes:
> On 5/16/10, Stefan Weil <weil@mail.berlios.de> wrote:
>> Am 15.05.2010 22:49, schrieb Blue Swirl:
>>
>>
>> > Hi,
>> >
>> > With this mingw32 compiler:
>> >
>> > $ i586-mingw32msvc-gcc -v
>> > Using built-in specs.
>> > Target: i586-mingw32msvc
>> > Configured with:
[...]
>> > build will not succeed because formats %zd, %zu, %hh, %lld, %llx and
>> > %llu are not known by the compiler.
>> >
>> > Any %ll* use is clearly a bug, we have PRI*64 macros just for this
>> purpose.
>> >
>> > For %hh and %z there may be better ways than these patches.
>> >
>> > With the patches I can build working Win32 binaries and there are no
>> warnings.
[...]
>> It's a compiler bug that the compiler does not know these format strings.
>> The code works nevertheless (at least with mingw libraries which are
>> not too old) because the format strings are interpreted by the C runtime
>> library.
>>
>> Is it worth changing a lot of files when we can expect a newer mingw
>> compiler version which works correctly for standard format strings?
>
> When and if that version becomes popular, PRIz* and the %hh hack could
> be removed or a compiler check could be added. But I don't think it's
> worth it, the macros are easy to use.
They're also ugly as sin.
next prev parent reply other threads:[~2010-05-17 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 20:49 [Qemu-devel] [PATCH 0/3] mingw32 compile fixes Blue Swirl
2010-05-15 21:39 ` Stefan Weil
2010-05-16 8:24 ` Blue Swirl
2010-05-17 8:37 ` Markus Armbruster [this message]
2010-05-17 16:01 ` Blue Swirl
2010-05-17 16:48 ` Markus Armbruster
2010-05-17 8:35 ` Markus Armbruster
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=m3vdamvs80.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.