From: Richard Henderson <richard.henderson@linaro.org>
To: eric.auger@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>
Cc: eric.auger.pro@gmail.com, pbonzini@redhat.com, paul@nowt.org,
qemu-devel@nongnu.org, peter.maydell@linaro.org,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH for 7.2?] target/i386: Remove compilation errors when -Werror=maybe-uninitialized
Date: Wed, 7 Dec 2022 12:23:45 -0600 [thread overview]
Message-ID: <64a40f5d-855e-7f70-ba1f-df464abcfddf@linaro.org> (raw)
In-Reply-To: <660c1fa1-3575-1849-01d0-8411ca4101d8@redhat.com>
On 12/7/22 10:08, Eric Auger wrote:
> On 12/7/22 16:55, Stefan Hajnoczi wrote:
>>> I am using this configure cmd line:
>>>
>>> ./configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib/qemu
>>> --target-list=x86_64-softmmu --docdir=/usr/share/doc/qemu --enable-kvm
>>> --extra-cflags=-O --enable-trace-backends=log --python=/usr/bin/python3
>>> --extra-cflags=-Wall --extra-cflags=-Wundef
>>> --extra-cflags=-Wwrite-strings --extra-cflags=-Wmissing-prototypes
>>> --extra-cflags=-fno-strict-aliasing --extra-cflags=-fno-common
>>> --extra-cflags=-Werror=type-limits
>>>> If you added it manually then let's fix this in 8.0 since it's not
>>>> tested/supported and very few people will see this issue.
>> Did you create the ./configure command-line manually? Do you think
>> other people will hit this?
> no I did not. I just tried to install a fresh qemu repo and just ran the
> above configure command.
Stefan's question is where did you get this configure command?
If it came from an rpm script or suchlike, we might take more notice than if this is just
you adding --extra-cflags for your own testing.
> I am actually surprised nobody hit that already.
Adding -Wall is not standard, nor all the other -W that you are adding. I think you
should not be surprised that you run into problems.
While you can make a case for auditing the code base and adding these to the default set
of warning flags, that's a job for the next development cycle.
r~
next prev parent reply other threads:[~2022-12-07 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 13:24 [PATCH for 7.2?] target/i386: Remove compilation errors when -Werror=maybe-uninitialized Eric Auger
2022-12-07 13:29 ` Eric Auger
2022-12-07 14:09 ` Stefan Hajnoczi
2022-12-07 14:33 ` Eric Auger
2022-12-07 15:55 ` Stefan Hajnoczi
2022-12-07 16:08 ` Eric Auger
2022-12-07 18:23 ` Richard Henderson [this message]
2022-12-07 18:44 ` Eric Auger
2022-12-07 20:28 ` Peter Maydell
2022-12-07 20:39 ` Eric Auger
2022-12-07 16:55 ` Philippe Mathieu-Daudé
2022-12-07 18:22 ` Eric Auger
2022-12-07 19:11 ` Stefan Weil via
2022-12-07 19:59 ` Stefan Hajnoczi
2022-12-07 20:11 ` Eric Auger
2022-12-07 19:59 ` Compiler warnings with maximum warning level (was: Re: [PATCH for 7.2?] target/i386: Remove compilation errors when -Werror=maybe-uninitialized) Stefan Weil via
2022-12-07 20:17 ` [PATCH for 7.2?] target/i386: Remove compilation errors when -Werror=maybe-uninitialized Eric Auger
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=64a40f5d-855e-7f70-ba1f-df464abcfddf@linaro.org \
--to=richard.henderson@linaro.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=paul@nowt.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/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).