From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ItBAk-0002Kc-Po for qemu-devel@nongnu.org; Fri, 16 Nov 2007 19:04:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ItBAj-0002KB-9d for qemu-devel@nongnu.org; Fri, 16 Nov 2007 19:04:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ItBAi-0002K6-V7 for qemu-devel@nongnu.org; Fri, 16 Nov 2007 19:04:29 -0500 Received: from bangui.magic.fr ([195.154.194.245]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1ItBAi-00089M-GY for qemu-devel@nongnu.org; Fri, 16 Nov 2007 19:04:28 -0500 Subject: Re: [Qemu-devel] RFC: fix for random Qemu crashes From: "J. Mayer" In-Reply-To: References: <1195168693.2415.19.camel@rapid> <200711161552.55645.paul@codesourcery.com> <1195229132.28318.10.camel@jma4.dev.netgem.com> Content-Type: text/plain Date: Sat, 17 Nov 2007 01:04:03 +0100 Message-Id: <1195257843.5335.15.camel@rapid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: andrzej zaborowski Cc: qemu-devel@nongnu.org, Paul Brook On Fri, 2007-11-16 at 21:32 +0100, andrzej zaborowski wrote: > On 16/11/2007, Jocelyn Mayer wrote: > > > > On Fri, 2007-11-16 at 15:52 +0000, Paul Brook wrote: > > > > Then, I choosed to replace 'inline' by 'always_inline', which is more > > > > invasive but have less risks of side effects. The diff is attached in > > > > always_inline.diff. > > > > The last thing that helps solve the problem is to change the inlining > > > > limits of gcc, at least to compile the op.o file. > > > > > > Presumably we only need one of the last two patches? It seems rather pointless > > > to have always_inline *and* change the inlining heuristics. > > > > >From the tests I made, it seems that adding always_inline helps but > > unfortunatelly does not solve all cases. Should check in the gcc source > > code why it is so... > > > > > I'm ok with using always_inline for op.o (and things it uses directly) as this > > > is required for correctness. I'm not convinced that that using always_inline > > > everywhere is such a good idea. > > > > That's exactly what I did: I changed 'inline' to 'always_inline' in > > headers that are included by op.c, I did not made any change in other > > headers. > > I think a line like > > #define inline __attribute__ (( always_inline )) inline > > in dyngen-exec.h should be As I already pointed it in the first message of the thread, this kind of define would expand recursivelly, which is particullary ugly, and which can in some cases lead to compiler warnings or errors. I already had this kind of problems using the linux kernel headers which preciselly uses this definitition. But, once again, adding always_inline to functions does not completelly solve the problem (please read the thread !) or at least does not solves it with all gcc versions. The inline growth limits tweaking seems needed too. -- J. Mayer Never organized