qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandriva.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] GCC 4 patches
Date: Mon, 14 Nov 2005 17:01:59 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0511141631150.27675@gauss.mandrakesoft.com> (raw)

Hi,

The following patches makes it possible to build QEMU with GCC 4 on x86.

However, there is still a problem with x86_64-softmmu. It may be a genuine
GCC bug though I don't see what's wrong with do_interrupt_real(). IOW, if
I build this function with GCC 3.3, x86_64-softmmu works fine, otherwise
QEMU hangs early. That's with GCC 4.0.3. With GCC 4.0.1, the problem looks
elsewhere, namely cpu-exec.c needs to be compiled with GCC 3 to work...

Anyhow, I am listing the current patches so that a GCC 4 compiled 
i386-softmmu binary works. Sorry, I don't have the time to look further 
the x86_64-softmmu problems.

Patches are available at:
<http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/contrib-SPECS/qemu/>

* qemu-0.7.0-gcc4.patch
  Original patch from Paul Brook + an addition to correctly decode imul.

* qemu-0.7.2-dyngen-check-stack-clobbers.patch
  Check stack is not clobbered in synthetic opcodes using GOTO_LABEL_PARAM
  [ this might exhibit a gcc4 performance regression though, insofar as 
  gcc4 feels the need to generate stack variables ]

* qemu-0.7.2-gcc4-hacks.patch
  Various workarounds to GCC ICEs.

* qemu-0.7.2-gcc4-opts.patch
  Don't generate stack variables for x86_64-softmmu case in functions
  using GOTO_LABEL_PARAM.

IMHO, it's not worth looking hard at compiling QEMU with GCC 4 on x86. The 
new hand written backend is a better alternative.

Bye,
Gwenolé.

             reply	other threads:[~2005-11-14 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 16:01 Gwenole Beauchesne [this message]
2005-11-14 19:45 ` [Qemu-devel] GCC 4 patches Fabrice Bellard

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=Pine.LNX.4.58.0511141631150.27675@gauss.mandrakesoft.com \
    --to=gbeauchesne@mandriva.com \
    --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).