From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1It3EW-0008S4-3V for qemu-devel@nongnu.org; Fri, 16 Nov 2007 10:35:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1It3EU-0008Ma-62 for qemu-devel@nongnu.org; Fri, 16 Nov 2007 10:35:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1It3EU-0008MD-0e for qemu-devel@nongnu.org; Fri, 16 Nov 2007 10:35:50 -0500 Received: from honiara.magic.fr ([195.154.193.36]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1It3ES-0007Zs-Ml for qemu-devel@nongnu.org; Fri, 16 Nov 2007 10:35:49 -0500 Received: from [172.17.17.137] (gw.netgem.com [195.68.2.34]) by honiara.magic.fr (8.13.1/8.13.1) with ESMTP id lAGFZar8007839 for ; Fri, 16 Nov 2007 16:35:36 +0100 Subject: Re: [Qemu-devel] RFC: fix for random Qemu crashes From: Jocelyn Mayer In-Reply-To: <473DB212.9010300@cs.helsinki.fi> References: <1195168693.2415.19.camel@rapid> <473DB212.9010300@cs.helsinki.fi> Content-Type: text/plain Date: Fri, 16 Nov 2007 16:35:48 +0100 Message-Id: <1195227348.28318.4.camel@jma4.dev.netgem.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: l_indien@magic.fr, 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 On Fri, 2007-11-16 at 17:06 +0200, Heikki Lindholm wrote: > J. Mayer kirjoitti: > > Some may have experienced of having some Qemu builds crashing, > > apparently at random places, but in a reproducable way. > > I found one reason for this crashes: it appears that with the growth of > > the op.c file, there may be cases where we could reach the inlining > > limits of gcc. In such a case, gcc would not inline some declared > > "inline" function but would emit a call and provide a separate function. > > Unfortunately, this is not acceptable in op.o context as it will > > slowdown the emulation and because the call is likely to break the > > specific compilation rules (ie reserved registers) used while compiling > > op.o > > Does -winline give a warning when this happens? I did not check this, but getting a warning won't help us a lot. The generated Qemu executable would still crash. -- Jocelyn Mayer