From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1It67y-0006ck-TL
	for qemu-devel@nongnu.org; Fri, 16 Nov 2007 13:41:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1It67x-0006bs-16
	for qemu-devel@nongnu.org; Fri, 16 Nov 2007 13:41:18 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1It67w-0006bo-Q6
	for qemu-devel@nongnu.org; Fri, 16 Nov 2007 13:41:16 -0500
Received: from mail.shareable.org ([81.29.64.88])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jamie@shareable.org>) id 1It67w-0004EX-43
	for qemu-devel@nongnu.org; Fri, 16 Nov 2007 13:41:16 -0500
Received: from mail.shareable.org (localhost [127.0.0.1])
	by mail.shareable.org (8.12.11.20060308/8.12.11) with ESMTP id
	lAGIfEjf013973
	for <qemu-devel@nongnu.org>; Fri, 16 Nov 2007 18:41:14 GMT
Received: (from jamie@localhost)
	by mail.shareable.org (8.12.11.20060308/8.12.8/Submit) id
	lAGFxTAr007295
	for qemu-devel@nongnu.org; Fri, 16 Nov 2007 15:59:29 GMT
Date: Fri, 16 Nov 2007 15:59:29 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] RFC: fix for random Qemu crashes
Message-ID: <20071116155929.GA28514@mail.shareable.org>
References: <1195168693.2415.19.camel@rapid> <473DB212.9010300@cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <473DB212.9010300@cs.helsinki.fi>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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?

And can it be repaired with __attribute__((__always_inline__))?

-- Jamie