From: Herbert Poetzl <herbert@13thfloor.at>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Removing GCC dependency
Date: Tue, 21 Dec 2004 16:36:33 +0100 [thread overview]
Message-ID: <20041221153633.GB9802@mail.13thfloor.at> (raw)
In-Reply-To: <200412211523.11342.paul@codesourcery.com>
On Tue, Dec 21, 2004 at 03:23:11PM +0000, Paul Brook wrote:
> > I always thought the current 'dyngen' solution as a temporary one
> > because it enabled a fast developpement of QEMU as the expense of
> > performance (this is relative of course, QEMU is already quite fast and
> > usable). But if we want better performances and better... portability
> > (in the sense that we are not tied to a specific GCC version), then a
> > hand coded code generator is the only way to go.
>
> Do we also want to aim towards using the same code generator for all guest
> cpus? We currently have separate op.c for each emulated architecture.
>
> Combining these into a single set of opcodes seems like a good idea. Once we
> start doing hand coded generator and/or nontrivial optimisations on the
> generated opcodes the duplications is really going to hurt, and the bar for
> adding new architectures will be significantly higher.
>
> I realise there complications with this (different register files and MMU
> types), but I can see large benefits if these can be overcome.
>
again a look at 'other' binary translators like the
bintrans[1] could provide some good ideas ...
best,
Herbert
-- from the README --
Machine Descriptions
--------------------
bintrans uses machine descriptions to automatically generate
interpreters, disassemblers, composer macros, and liveness analysers.
Currently, there are machine descriptions for the i386, the PPC and
the Alpha, residing in the files "i386.lisp", "ppc.lisp", and
"alpha.lisp", respectively.
Should you choose to play around with them, here's how to generate the
various C files from them:
1. Start CLISP
2. (load "init.lisp")
then:
3a. (generate-all-alpha-files) ; to generate the Alpha files
3b. (generate-all-ppc-files) ; to generate the PPC files
3c. (generate-all-intel-files) ; to generate the i386 files
> Paul
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-12-21 15:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 13:47 [Qemu-devel] get_func() hangs with gcc 3.4.2 on MinGW and WinXP host tomba
2004-12-15 14:18 ` Johannes Schindelin
2004-12-15 14:59 ` tomba
2004-12-15 23:45 ` Jim C. Brown
2004-12-15 23:52 ` Johannes Schindelin
2004-12-17 18:56 ` Juergen Lock
2004-12-18 0:09 ` Johannes Schindelin
2004-12-18 4:04 ` Jim C. Brown
2004-12-18 14:59 ` Johannes Schindelin
2004-12-18 15:50 ` Jim C. Brown
2004-12-19 14:25 ` Johannes Schindelin
2004-12-19 22:57 ` Jim C. Brown
2004-12-18 21:07 ` John R. Hogerhuis
2004-12-18 21:59 ` Jim C. Brown
2004-12-19 14:45 ` Johannes Schindelin
2004-12-20 6:26 ` John R. Hogerhuis
2004-12-20 15:16 ` Removing GCC dependency, was " Johannes Schindelin
2004-12-20 18:02 ` John R. Hogerhuis
2004-12-20 23:30 ` Fabrice Bellard
2004-12-21 14:36 ` [Qemu-devel] Testing with Win2k SP3 and Win2kSP4 Elefterios Stamatogiannakis
2004-12-21 15:23 ` [Qemu-devel] Re: Removing GCC dependency Paul Brook
2004-12-21 15:36 ` Herbert Poetzl [this message]
2004-12-19 22:13 ` [Qemu-devel] get_func() hangs with gcc 3.4.2 on MinGW and WinXP host Fabrice Bellard
2004-12-19 22:29 ` Johannes Schindelin
2004-12-20 3:31 ` Rob Browning
2004-12-20 18:57 ` John R. Hogerhuis
2005-01-17 14:16 ` CMinusMins, was " Johannes Schindelin
2005-01-17 15:36 ` malc
2005-01-17 15:53 ` Jim C. Brown
2005-01-17 16:13 ` OCAML, was " Mark A. Williamson
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=20041221153633.GB9802@mail.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=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).