qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] Re: [PATCH 2/6] qemu fixes
Date: Fri, 28 Nov 2008 12:44:33 +0100	[thread overview]
Message-ID: <492FD9A1.5030400@siemens.com> (raw)
In-Reply-To: <200811281131.27737.Christoph.Egger@amd.com>

Christoph Egger wrote:
> Hi,
> 
> This is a series of four patches which improve support
> for qemu on NetBSD.
> 
> Attached patch fixes warnings in the i386 specific part.
> 
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> 

Except for ss* in [copy, paste, sigh]...

> @@ -2275,8 +2275,8 @@
>                              int shift, int next_eip_addend)
>  {
>      int new_stack, i;
> -    uint32_t e1, e2, cpl, dpl, rpl, selector, offset, param_count;
> -    uint32_t ss, ss_e1, ss_e2, sp, type, ss_dpl, sp_mask;
> +    uint32_t e1 = 0, e2 = 0, cpl, dpl, rpl, selector, offset, param_count;
> +    uint32_t ss = 0, ss_e1 = 0, ss_e2 = 0, sp, type, ss_dpl, sp_mask;
>      uint32_t val, limit, old_sp_mask;
>      target_ulong ssp, old_ssp, next_eip;
>  

I have a better patch here that fixes the root of gcc's confusion:
missing noreturn instrumentation. The detection of the initialization of
ss* variables falls into the category "gcc isn't smart enough", and one
may discuss if we should handle it or wait for gcc getting smarter. BTW,
this patch is not BSD specific but gcc4 related.

Nevertheless, warning reduction patches are generally welcome IMHO!

Jan

  reply	other threads:[~2008-11-28 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 10:31 [Qemu-devel] [PATCH 2/6] qemu fixes Christoph Egger
2008-11-28 11:44 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-28 12:01 [Qemu-devel] " Christoph Egger

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=492FD9A1.5030400@siemens.com \
    --to=jan.kiszka@siemens.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 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).