qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>
Subject: Re: [Qemu-devel] WE NEED GCC 4 please
Date: Mon, 21 Jan 2008 14:51:00 +0100	[thread overview]
Message-ID: <200801211451.00621.jseward@acm.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0801211255410.5731@racer.site>


> > > As it is, Fabrice's code generator will most likely be something
> > > similar to Paul's qops, which means that you have to invent a
> > > "primitive C" in which to write the miniops, and you will have to
> > > write a backend for _each_ and _every_ host CPU you support.

It's not a terribly big deal.  Writing backends is a lot easier than
writing front ends, since the back end can just emit some small convenient
subset of target instructions, whereas the front ends have to deal
with every stupid, obscure, weird-ass instruction that ever shows up.

QEMU is not the first project to post-process gcc's output.  The
Glasgow Haskell Compiler
(http://en.wikipedia.org/wiki/Glasgow_Haskell_Compiler)
did that for many years and it was always an immense amount of
hassle tracking the changes to gcc's code generation.  Having a
completely-independent-of-everything, standalone code generator is
definitely a lot easier in the end.

> Given the unwillingness of Fabrice to rely on some external project,
> though, I gave up even before I had something even rudimentary.

Perhaps Fabrice could commit this code generator on a branch, even if
it is not perfect yet.  That would at least provide something "real"
to assess; so far all we have is rumour and speculation.

J

  reply	other threads:[~2008-01-21 13:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20 19:31 Re : [Qemu-devel] WE NEED GCC 4 please Sylvain Petreolle
2008-01-20 20:11 ` Mike Frysinger
2008-01-20 21:14   ` Johannes Schindelin
2008-01-20 22:26     ` Mike Frysinger
2008-01-20 22:38       ` Sunil Amitkumar Janki
2008-01-20 22:56         ` Mike Frysinger
2008-01-20 23:04           ` Philip Boulain
2008-01-20 22:59         ` Andreas Färber
2008-01-20 23:40           ` Johannes Schindelin
2008-01-21  3:39             ` Mulyadi Santosa
2008-01-21  7:19               ` Alexander Graf
2008-01-21 11:18               ` Johannes Schindelin
2008-01-21 11:30                 ` Mulyadi Santosa
2008-01-21 12:45                 ` Andreas Färber
2008-01-21 13:02                   ` Johannes Schindelin
2008-01-21 13:51                     ` Julian Seward [this message]
2008-01-21 14:58                 ` Ronan Keryell
2008-01-21 15:36                   ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2008-01-20  2:34 renatogallo
2008-01-20 18:40 ` Jérôme PRIOR

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=200801211451.00621.jseward@acm.org \
    --to=jseward@acm.org \
    --cc=andreas.faerber@web.de \
    --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).