From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] help porting to BF533
Date: Sun, 20 Jun 2004 17:09:06 -0700 [thread overview]
Message-ID: <1087776546.21945.201.camel@aragorn> (raw)
In-Reply-To: <32848.81.199.255.141.1087770276.squirrel@81.199.255.141>
dyngen must be ported to at least one library format per processor QEMU
is used with.
For example, on x86, ELF would have been enough. Generate the code to
ELF, then it must be read back in so that the lengths of each code block
and relocation information can be determined.
The folks that did the Windows port went the extra mile and ported
dyngen to COFF.
In fact it would be completely reasonable to use the dynamically
generated primitives from a Linux ELF file on a COFF platform.
However, I don't know anything about the Blackfin BF533 and bflt.
My guess is you will have to completely port dyngen over to that
platform. I see you becoming intimately familiar with bflt in the near
future :-)
-- John.
next prev parent reply other threads:[~2004-06-21 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 22:24 [Qemu-devel] help porting to BF533 alonl
2004-06-21 0:09 ` John R. Hogerhuis [this message]
2004-06-22 5:31 ` kazu
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=1087776546.21945.201.camel@aragorn \
--to=jhoger@speakeasy.net \
--cc=jhoger@pobox.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).