qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: l_indien@magic.fr, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: fix for random Qemu crashes
Date: Fri, 16 Nov 2007 17:42:17 +0200	[thread overview]
Message-ID: <473DBA59.9030602@cs.helsinki.fi> (raw)
In-Reply-To: <1195227348.28318.4.camel@jma4.dev.netgem.com>

Jocelyn Mayer kirjoitti:
> 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.

But a warning makes the problem more noticable. I tried -Winline and it 
does give warnings, but I'm not sure whether I'm hitting the same 
behaviour you see. I silenced the lot with 
--param-max-inline-insns-single=4000

-- Heikki Lindholm

  reply	other threads:[~2007-11-16 15:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 23:18 [Qemu-devel] RFC: fix for random Qemu crashes J. Mayer
2007-11-15 23:49 ` andrzej zaborowski
2007-11-16  0:09   ` J. Mayer
2007-11-16 15:06 ` Heikki Lindholm
2007-11-16 15:35   ` Jocelyn Mayer
2007-11-16 15:42     ` Heikki Lindholm [this message]
2007-11-16 16:34       ` Jocelyn Mayer
2007-11-16 15:59   ` Jamie Lokier
2007-11-16 20:13     ` Jocelyn Mayer
2007-11-16 15:52 ` Paul Brook
2007-11-16 16:05   ` Jocelyn Mayer
2007-11-16 20:32     ` andrzej zaborowski
2007-11-17  0:04       ` J. Mayer
2007-11-17  2:58         ` [Qemu-devel] " Ben Pfaff
2007-11-17  8:22           ` J. Mayer
2007-11-17 10:57         ` [Qemu-devel] " andrzej zaborowski
2007-11-17 11:13           ` J. Mayer
  -- strict thread matches above, loose matches on Subject: below --
2007-11-18 15:48 [Qemu-devel] [RFC] Fix " J. Mayer

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=473DBA59.9030602@cs.helsinki.fi \
    --to=holindho@cs.helsinki.fi \
    --cc=l_indien@magic.fr \
    --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).