qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Aleksandar Markovic <amarkovic@wavecomp.com>,
	Stefan Markovic <smarkovic@wavecomp.com>
Subject: Re: [Qemu-devel] [PATCH for-3.1 0/2] Fix disas/nanomips
Date: Tue, 27 Nov 2018 12:36:57 +0000	[thread overview]
Message-ID: <CAFEAcA_gWYGnD2cAdGRWKKZRfddPvgQoS89nxM8=ro++fO+Gmw@mail.gmail.com> (raw)
In-Reply-To: <20181127121724.19755-1-sw@weilnetz.de>

On Tue, 27 Nov 2018 at 12:17, Stefan Weil <sw@weilnetz.de> wrote:
>
> These two patches fix wrong format strings used in disas/nanomips.
>
> The first patch replaces proprietary data types by POSIX data types,
> because otherwise the PRI... macros cannot be used in the second patch.

I think this is a good idea, but that first patch is a huge patch for
this point in the 3.1 release cycle. Can we fix the warnings
by just casting the arguments to the img::format() function ?

> Those patches are only relevant for 3.1 if full nanomips support is considered
> important enought and if QEMU is used on big endian machines (I think
> the old code will work on little endian hosts even with wrong format
> strings).

It only affects the disassembler, which is a debug tool.
A week ago this would have been a fairly definite "yes, fix it"
issue; at this point, with rc3 due to go out today, it's a bit
trickier to justify. (rc3 will be the last rc unless any showstopper
issues turn up.)

> I use those patches for QEMU for Windows because that is compiled with
> more compiler warnings, so compilation would fail without the fix.

My Windows cross-compiler builds work OK, FWIW, and -Werror is
only enabled by default for Linux builds, so warnings shouldn't
result in build failures.

thanks
-- PMM

  parent reply	other threads:[~2018-11-27 12:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 12:17 [Qemu-devel] [PATCH for-3.1 0/2] Fix disas/nanomips Stefan Weil
2018-11-27 12:17 ` [Qemu-devel] [PATCH for-3.1 1/2] disas/nanomips: Replace proprietary by POSIX data types Stefan Weil
2018-11-27 12:17 ` [Qemu-devel] [PATCH for-3.1 2/2] disas/nanomips: Fix format strings Stefan Weil
2018-12-23 17:10   ` Aleksandar Markovic
2018-12-23 20:30     ` Stefan Weil
2018-11-27 12:36 ` Peter Maydell [this message]
2018-11-27 12:58   ` [Qemu-devel] [PATCH for-3.1 0/2] Fix disas/nanomips Stefan Weil
2018-11-28  6:50 ` Aleksandar Markovic
2018-11-29  6:36 ` no-reply

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='CAFEAcA_gWYGnD2cAdGRWKKZRfddPvgQoS89nxM8=ro++fO+Gmw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=smarkovic@wavecomp.com \
    --cc=sw@weilnetz.de \
    /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).