qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: sinisa marovic <sinisamarovic@yahoo.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Porting QEMU to PalmOS
Date: Wed, 23 May 2007 11:48:59 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705231145390.4113@racer.site> (raw)
In-Reply-To: <235654.95127.qm@web54602.mail.re2.yahoo.com>

Hi,

On Wed, 23 May 2007, sinisa marovic wrote:

> Relocation types that fail are 25 and 26, which are R_ARM_GOTPC and 
> R_ARM_GOT32 respectively. Their names are:
> 
> _GLOBAL_OFFSET_TABLE_
> cc_table
> __op_param1
> __op_param2
> __op_param3
> 
> Is there a way to fix this?

The GOT is an offset table. Many CPUs have fixed-size instruction sets, 
which means that you cannot easily jump to an absolute address, since the 
address alone would already fill up the size.

Of course, this is a no-no for QEmu, since the _same_ function snippet 
will be reused _multiple_ times. So, the address must not come from a GOT, 
but be inserted directly into the code.

I do not remember off-hand how I managed to do this a couple of years ago, 
when I worked on a MIPS host, but there _are_ gcc options to avoid a GOT.

Hth,
Dscho

  reply	other threads:[~2007-05-23 10:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  9:07 [Qemu-devel] Porting QEMU to PalmOS sinisa marovic
2007-05-23 10:48 ` Johannes Schindelin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23 11:20 sinisa marovic
2007-05-23 15:23 ` Wolfgang Schildbach
2007-05-23 22:02   ` Jonathan Kalbfeld
2007-05-24 21:18   ` Jonathan Kalbfeld
2007-05-24 23:19 sinisa marovic
2007-05-24 23:33 ` Jonathan Kalbfeld
2007-05-25  5:37   ` Jason Brand
2007-05-24 23:47 sinisa marovic
2007-06-04 15:33 sinisa marovic
2007-07-01 12:29 ` andrzej zaborowski
2007-07-01 17:20   ` Luke-Jr
2007-07-01 18:08     ` Johannes Schindelin
2007-07-01 18:16     ` andrzej zaborowski

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.64.0705231145390.4113@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=sinisamarovic@yahoo.com \
    /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).