qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Ronan Keryell <Ronan.Keryell@enstb.org>
Subject: Re: [Qemu-devel] WE NEED GCC 4 please
Date: Mon, 21 Jan 2008 15:36:04 +0000	[thread overview]
Message-ID: <200801211536.05794.paul@codesourcery.com> (raw)
In-Reply-To: <874pd7ns30.fsf@an-dro.enstb.org>

> Well, what about adding a new backend phase to gcc generating what we
> expect for our purpose? Ok, it is rather easy to have a branch in gcc,
> harder to have it accepted in the main-stream gcc... :-) With a good
> argumentation...

IMHO (as a full time gcc developer) it's easier to just implement a code 
generator from scratch.

Paul

  reply	other threads:[~2008-01-21 15:36 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
2008-01-21 14:58                 ` Ronan Keryell
2008-01-21 15:36                   ` Paul Brook [this message]
  -- 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=200801211536.05794.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=Ronan.Keryell@enstb.org \
    --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).