From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [5055] Handle terminating signals (Gerd Hoffmann)
Date: Fri, 22 Aug 2008 08:50:27 -0500 [thread overview]
Message-ID: <48AEC423.4030105@codemonkey.ws> (raw)
In-Reply-To: <48AEBD30.40008@siemens.com>
Jan Kiszka wrote:
> Anthony Liguori wrote:
>
>> I do check for warnings. The version of GCC I'm using (3.4.6 20060404
>> (Red Hat 3.4.6-9)) does not complain about these things. We probably
>> should add -Wall to the build and take the time to fix up all of the
>> warnings that occur.
>>
>
> Makes /me wonder why 3.4 thinks there is no problem here (while this is
> obviously wrong).
>
> Being lazy and SuSE-based (which only provides a 3.3.3 for such legacy
> use cases, IIRC), and also remembering vaguely that there used to be
> warnings about 3.4 /wrt qemu, I kept 3.3.3.
>
Could just be that more warnings are enabled by default with your
particular version of GCC.
> BTW, do you also check for 64-bit issues? My feeling is that this - at
> least - used to be a rare host platform for qemu contributors.
>
I run a 64-bit host.
I run Fedora 9 x86_64. I have as many optional libraries installed as
possible. I also have a mingw32 cross compiler setup that I use to test
the windows build. The mingw32 compiler is gcc4 and throws an awful lot
of warnings.
Regards,
Anthony Liguori
> Jan
>
>
next prev parent reply other threads:[~2008-08-22 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 20:08 [Qemu-devel] [5055] Handle terminating signals (Gerd Hoffmann) Anthony Liguori
2008-08-22 10:48 ` [Qemu-devel] " Jan Kiszka
2008-08-22 11:32 ` Gerd Hoffmann
2008-08-22 11:55 ` Jan Kiszka
2008-08-22 12:06 ` Gerd Hoffmann
2008-08-22 13:21 ` Jan Kiszka
2008-08-22 12:52 ` Anthony Liguori
2008-08-22 13:20 ` Jan Kiszka
2008-08-22 13:50 ` Anthony Liguori [this message]
2008-09-02 11:21 ` Jan Kiszka
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=48AEC423.4030105@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.