From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Christian Roue <croue7@gmail.com>
Subject: Re: [Qemu-devel] Patch for compiling with GCC 4
Date: Sat, 16 Feb 2008 20:01:01 +0000 [thread overview]
Message-ID: <200802162001.02410.paul@codesourcery.com> (raw)
In-Reply-To: <ef99d6f80802160322k7a753cddh9144b87df1d1e0f4@mail.gmail.com>
On Saturday 16 February 2008, Christian Roue wrote:
> Hi all,
> I tried to compile qemu cvs head on my x86_64 linux with gcc 4.1.2 using
> --disable-gcc-check, I found compile fails as stated in configure before i
> disabled gcc check..
> Error message, points to a problem of dyngen not correctly detecting
> function ends on i386 when last instruction is a jump. I applied following
> change and successfully compiled/run qemu i386. This extra test check for
> a relative backward jump to function exit ret,
> gcc 4 apparently generates a few of these.
You patch is wrong. The dyngen error is correct.
Paul
next prev parent reply other threads:[~2008-02-16 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 11:22 [Qemu-devel] Patch for compiling with GCC 4 Christian Roue
2008-02-16 20:01 ` Paul Brook [this message]
2008-02-17 20:22 ` Christian Roue
2008-02-18 12:07 ` Alexander Graf
2008-02-18 19:52 ` Christian Roue
2008-02-18 20:49 ` Thiemo Seufer
2008-02-19 19:12 ` Christian Roue
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=200802162001.02410.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=croue7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.