qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compile fixes for newer gcc
Date: Tue, 10 May 2005 22:10:59 +0100	[thread overview]
Message-ID: <200505102210.59973.paul@codesourcery.com> (raw)
In-Reply-To: <1115758043.29701.14.camel@rapid>

On Tuesday 10 May 2005 21:47, J. Mayer wrote:
> On Mon, 2005-05-09 at 02:49 +0100, Paul Brook wrote:
> > The attached patch fixes some trivial build problems with newer gcc on
> > amd64. It adds FORCE_RET on load ops,
>
> Index: target-ppc/exec.h
> ===================================================================
> RCS file: /cvsroot/qemu/qemu/target-ppc/exec.h,v
> retrieving revision 1.10
> diff -u -p -r1.10 exec.h
> --- target-ppc/exec.h   13 Mar 2005 17:01:22 -0000      1.10
> +++ target-ppc/exec.h   9 May 2005 01:33:04 -0000
> @@ -33,11 +33,7 @@ register uint32_t T2 asm(AREG3);
>  #define FT1 (env->ft1)
>  #define FT2 (env->ft2)
>
> -#if defined (DEBUG_OP)
> -#define RETURN() __asm__ __volatile__("nop");
> -#else
> -#define RETURN() __asm__ __volatile__("");
> -#endif
> +#define RETURN() FORCE_RET()
>
> Please don't change this. This is usefull and your so-called "fix" only
> makes debug harder.
> Same goes for all other patches: use RETURN macro everywhere in PowerPC
> emulation code.

Ok. This slipped in from a following patch, so we can revisit it when I submit 
those changes. A much better way to do this is to add the NOPs in dyngen. 
Then you get nops after all ops, not just the ones that use RETURN()

> >  and introduces helper functions for floating
> > point negation (these require a literal constant load).
>
> /* fneg */
> +void do_fneg (void);
>  PPC_OP(fneg)
>  {
> -    FT0 = -FT0;
> +    do_fneg();
>      RETURN();
>  }
>
> Where's the problem ? It compiles and run perfectly on my amd64. Calling
> a function for this is a nonsense. Don't apply this.

As I said it's required to avoid a pc-relative constant literal load.
gcc4.0 compiles fneg to:

movlpd 0x1288(%rbp),%xmm0
xorpd  0(%rip),%xmm0        # 3e50 <op_fneg+0x10>
     R_X86_64_PC32     .LC0+0xfffffffffffffffc
movsd  %xmm0,0x1288(%rbp)

Which dyngen can't grok.

> I will do an update to use softfloat functions everywhere in PowerPC
> emulation one of those days...

That would be great.
 
Paul

  reply	other threads:[~2005-05-10 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09  1:49 [Qemu-devel] Compile fixes for newer gcc Paul Brook
2005-05-10 20:47 ` J. Mayer
2005-05-10 21:10   ` Paul Brook [this message]
2005-05-11 21:20     ` 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=200505102210.59973.paul@codesourcery.com \
    --to=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).