From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L61m2-00016w-Fu for qemu-devel@nongnu.org; Fri, 28 Nov 2008 06:44:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L61m0-00016i-5t for qemu-devel@nongnu.org; Fri, 28 Nov 2008 06:44:37 -0500 Received: from [199.232.76.173] (port=60346 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L61lz-00016f-WE for qemu-devel@nongnu.org; Fri, 28 Nov 2008 06:44:36 -0500 Received: from gecko.sbs.de ([194.138.37.40]:24696) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L61lz-0007I9-8p for qemu-devel@nongnu.org; Fri, 28 Nov 2008 06:44:35 -0500 Message-ID: <492FD9A1.5030400@siemens.com> Date: Fri, 28 Nov 2008 12:44:33 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <200811281131.27737.Christoph.Egger@amd.com> In-Reply-To: <200811281131.27737.Christoph.Egger@amd.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 2/6] qemu fixes Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl 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 > 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