From: Herbert Poetzl <herbert@13thfloor.at>
To: alonl@tiranogath.dnsalias.net
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] dyngen porting - workaround for st_size==0
Date: Thu, 8 Jul 2004 01:36:07 +0200 [thread overview]
Message-ID: <20040707233607.GA3446@MAIL.13thfloor.at> (raw)
In-Reply-To: <12782.194.90.80.211.1089205601.squirrel@194.90.80.211>
On Wed, Jul 07, 2004 at 04:06:41PM +0300, alonl@tiranogath.dnsalias.net wrote:
> Hi,
>
> I'm compiling qemu using the nisa-elf compiler, a cross compiler for the
> BF533, a dsp by analog devices. After some tweaking I managed to compile
> dyngen and a bunch of other files, until the point where dyngen is
> executed to create op.h and opc.h.
>
> At that point I get error messages that complain about empty code for
> _op_SOMETHING (sorry for no pasted make logs - I'm writing this on a
> different machine. btw the added underscore is a change I had to make
> since the nisa-elf compiler produces function symbols with that
> underscore prepended). I looked into dyngen and found that it was ok, the
> problem is that the elf objects that nisa-elf-gcc produces have
> sym->st_size == 0! This doesn't prevent them from running at the end, but
> it prevents me from compiling qemu.. let alone running it..
>
> I can't change the st_size field without hacking the toolchain, which is
> very hard - is there any way to make dyngen work without the size field?
> will any of the following work:
> sort the symbols according to st_value (address), and take the difference
> to be the size that the JIT should copy.
> or: from st_value look for the RTS opcode (10 00 for the BF533, a 16 bit
> instruction processor), assuming there is only one for each function.
how about that: define a label at the end of the
code, something like _op_SOMETHING_end, and just
use/store the difference between this and the _op
symbol ...
> Any other ideas are appreciated, help!
HTH,
Herbert
> Alon
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
prev parent reply other threads:[~2004-07-07 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 13:06 [Qemu-devel] dyngen porting - workaround for st_size==0 alonl
2004-07-07 23:36 ` Herbert Poetzl [this message]
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=20040707233607.GA3446@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=alonl@tiranogath.dnsalias.net \
--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).