All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch: Sparc system support
Date: Sat, 02 Oct 2004 01:06:43 +0200	[thread overview]
Message-ID: <1096672003.10524.16.camel@rapid> (raw)
In-Reply-To: <Pine.LNX.4.58.0410011752210.7896@wgmdd8.biozentrum.uni-wuerzburg.de>

On Fri, 2004-10-01 at 18:00, Johannes Schindelin wrote:
> Hi,

Hi,

> On Fri, 1 Oct 2004, Renzo Davoli wrote:
> 
> > In fact there is something wrong in the op.h file:
> >
> > Line 4778:
> > case INDEX_op_fitos: {
> >     extern void op_fitos();
> >     memcpy(gen_code_ptr, (void *)((char *)&op_fitos+0), 56);
> >     *(uint16_t *)(gen_code_ptr + 26) = ((long)(&) + 0 + 0x8000) >> 16;
> >     *(uint16_t *)(gen_code_ptr + 30) = ((long)(&) + 0);
> >     gen_code_ptr += 56;
> > }
> >
> > (long)(&) .... the operand is missing.
> 
> This most likely means that your op.o has a relocation without a proper
> symbol name. This can happen if a relocation is split into loword
> and hiword on some architectures. What host are you compiling for?

I also had issues like this with PPC some opcodes. I noticed that this
happened when gcc uses local variables. The solution I found was to
rewrite some micro-operations to make them simpler to compile and make
others helper functions (so the micro-op is just a function call), for
the more complex ones.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2004-10-01 23:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 16:01 [Qemu-devel] Patch: Sparc system support Blue Swirl
2004-09-30 22:23 ` Fabrice Bellard
2004-10-01 14:10   ` Renzo Davoli
2004-10-01 16:00     ` Johannes Schindelin
2004-10-01 23:06       ` J. Mayer [this message]
2004-10-02  3:50         ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2004-10-02 11:07 Blue Swirl
2004-10-02 13:07 ` Fabrice Bellard
2004-10-03  7:37 Blue Swirl

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=1096672003.10524.16.camel@rapid \
    --to=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 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.