From: Stefan Weil <sw@weilnetz.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] w64: Fix compiler warning [-Wformat]
Date: Sat, 11 Aug 2012 21:15:30 +0200 [thread overview]
Message-ID: <5026AF52.2060805@weilnetz.de> (raw)
In-Reply-To: <CAAu8pHvj_GTYDh-rKZKwJ-mxtWsy1fW9Ld0k3CnYqs-Nv_KDoQ@mail.gmail.com>
Am 11.08.2012 16:42, schrieb Blue Swirl:
> On Fri, Aug 10, 2012 at 7:45 PM, Stefan Weil <sw@weilnetz.de> wrote:
>> Glib2 uses __printf__ in macro G_GNUC_PRINTF for printf like
>> functions. For MinGW, we want __gnu_printf__ because we use
>> POSIX format specifiers instead of the MS format specifiers.
> I get these warnings from glib:
> CC trace/control.o
> In file included from
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gthread.h:34,
> from
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gasyncqueue.h:34,
> from /usr/local/i686-mingw32msvc/include/glib-2.0/glib.h:34,
> from /src/qemu/qemu-common.h:40,
> from /src/qemu/trace/control.h:13,
> from /src/qemu/trace/default.c:10:
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gerror.h:46:
> warning: '__gnu_printf__' is an unrecognized format function type
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gerror.h:70:
> warning: '__gnu_printf__' is an unrecognized format function type
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gerror.h:88:
> warning: '__gnu_printf__' is an unrecognized format function type
> /usr/local/i686-mingw32msvc/include/glib-2.0/glib/gerror.h:94:
> warning: '__gnu_printf__' is an unrecognized format function type
Oh, sorry, I forgot that older versions of gcc (before 4.4)
don't support __gnu_printf__.
I'll have to modify my patch...
Regards,
Stefan W.
prev parent reply other threads:[~2012-08-11 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 19:45 [Qemu-devel] [PATCH] w64: Fix compiler warning [-Wformat] Stefan Weil
2012-08-11 14:42 ` Blue Swirl
2012-08-11 19:15 ` Stefan Weil [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=5026AF52.2060805@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.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.