qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Roue" <croue7@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch for compiling with GCC 4
Date: Sun, 17 Feb 2008 21:22:32 +0100	[thread overview]
Message-ID: <ef99d6f80802171222r1c234f98re80151129f685d8a@mail.gmail.com> (raw)
In-Reply-To: <200802162001.02410.paul@codesourcery.com>

Well, I somehow felt like it was a bit brutal and probably fixing the
symptoms which is apparently the case.
Looking more carefully, compile fails in :
sh4-linux-user for function op_cmp_str_T0_T1
gcc optimization leads to a ret followed by a last assignement with a jump back.
I guess dyngen hopes to find function epilogue as the last bytes.
It's apparently the only function where it happens.

I found that adding gcc option "-fno-tree-dominator-opts" for sh4
target avoids this (I suppose) unwanted optimization.
It may be a bit brutal again ( disabling too many optims or wrong ones).
May be the op_cmp_str_T0_T1 function can be rewritten to something
that avoids this optimization.
Am I on a better track ?

Bye
Chris.


On Feb 16, 2008 9:01 PM, Paul Brook <paul@codesourcery.com> wrote:
> 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
>

  reply	other threads:[~2008-02-17 20:22 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
2008-02-17 20:22   ` Christian Roue [this message]
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=ef99d6f80802171222r1c234f98re80151129f685d8a@mail.gmail.com \
    --to=croue7@gmail.com \
    --cc=paul@codesourcery.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).