From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Liviu Ionescu <ilg@livius.net>, QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MinGW build
Date: Fri, 28 Nov 2014 08:14:16 +0100 [thread overview]
Message-ID: <547820C8.3060805@weilnetz.de> (raw)
In-Reply-To: <CAFEAcA-y9oTZW2YnQGDH=W3VCW6_hfHy7W0B41jLSo+DyJE1Dw@mail.gmail.com>
Am 27.11.2014 um 21:18 schrieb Peter Maydell:
> On 27 November 2014 at 20:09, Stefan Weil <sw@weilnetz.de> wrote:
>> *nearly means that there are still warnings for format strings in C++
>> code.
>
> Hmm, do we still have these with the libvixl version we have
> now? If so, could you forward me a copy of them and I'll see
> if I can persuade upstream to fix them...
>
> thanks
> -- PMM
>
The libvixl code is correct, but the C++ compiler would need to be
fixed. Here are some examples:
disas/libvixl/a64/disasm-a64.cc:1340:57: warning: unknown conversion
type character ‘l’ in format [-Wformat]
disas/libvixl/a64/disasm-a64.cc:1340:57: warning: too many arguments for
format [-Wformat-extra-args]
disas/libvixl/a64/disasm-a64.cc:1492:42: warning: unknown conversion
type character ‘l’ in format [-Wformat]
That code uses PRIx64, so the format specifier is %llx which is correct.
Obviously the C++ compiler ignores that QEMU uses ANSI format specifiers
(compiler option -D__USE_MINGW_ANSI_STDIO=1) instead of the MS specific
ones.
A simple workaround for QEMU would just suppress -Wformat and
-Wformat-extra-args for C++ code.
Regards
Stefan
next prev parent reply other threads:[~2014-11-28 7:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:55 [Qemu-devel] MinGW build Liviu Ionescu
2014-11-26 20:13 ` Peter Maydell
2014-11-26 20:19 ` Stefan Weil
2014-11-26 21:44 ` Liviu Ionescu
2014-11-27 16:43 ` Liviu Ionescu
2014-11-27 19:34 ` Peter Maydell
2014-11-27 19:57 ` Liviu Ionescu
2014-11-27 20:09 ` Stefan Weil
2014-11-27 20:14 ` Liviu Ionescu
2014-11-27 20:18 ` Peter Maydell
2014-11-27 20:27 ` Liviu Ionescu
2014-11-27 22:04 ` Peter Maydell
2014-11-28 0:30 ` Liviu Ionescu
2014-11-28 7:14 ` Stefan Weil [this message]
2014-11-28 8:41 ` Peter Maydell
2015-11-27 18:49 ` Peter Maydell
2015-11-27 19:16 ` Stefan Weil
2015-11-27 21:05 ` Peter Maydell
2015-11-29 12:03 ` Juan Quintela
2015-12-03 11:58 ` Peter Maydell
2015-12-03 14:15 ` Peter Maydell
2015-12-03 14:30 ` Juan Quintela
2015-11-30 13:24 ` Juan Quintela
2015-11-30 13:29 ` Stefan Weil
2014-11-27 20:52 ` Liviu Ionescu
2014-11-27 21:14 ` Stefan Weil
2014-11-27 21:38 ` Liviu Ionescu
2014-11-28 6:20 ` Stefan Weil
2014-11-28 6:23 ` Liviu Ionescu
2014-11-28 7:03 ` Stefan Weil
2014-12-01 10:30 ` Liviu Ionescu
2014-12-01 18:42 ` Stefan Weil
2014-12-02 18:28 ` Liviu Ionescu
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=547820C8.3060805@weilnetz.de \
--to=sw@weilnetz.de \
--cc=Qemu-devel@nongnu.org \
--cc=ilg@livius.net \
--cc=peter.maydell@linaro.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).