qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: "Steve D. Perkins" <lists@steveperkins.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch Submission] QEMU with GCC/Win32
Date: Sun, 31 Jul 2005 00:39:57 +0100	[thread overview]
Message-ID: <200507310039.59060.paul@codesourcery.com> (raw)
In-Reply-To: <42EC0A39.40404@steveperkins.net>

>     Given that QEMU can support the current release of GCC on Windows by
> changing less than 40 lines of code in one file, can we please begin
> discussing the inclusion of these changes in the main codebase?
> Explicitly specifying this one variable name in a preprocessor directive
> doesn't look as if it would affect builds on other platforms, but it
> would be easy enough to test either way.

My 6-line gen_op_label patch should be safe, and isn't unintrusive, so IMHO 
should be applied.

The gcc4 changes are a different matter.  I discusses this with Fabrice on IRC 
shortly after submitting the patch. The patch is pretty invasive, high risk, 
and potentially hard to debug and maintain. Given this it's not clear if it's 
worth the hassle just to support gcc4.

It's generally agreed that the long term solution is to replace dyngen with a 
hand coded generator. I'm working on this, but there's still quite a bit to 
do.

Paul

  reply	other threads:[~2005-07-31  0:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30 18:42 [Qemu-devel] [Patch Submission] QEMU with GCC/Win32 Steve D. Perkins
2005-07-30 19:13 ` Paul Brook
2005-07-30 19:41   ` Steve D. Perkins
2005-07-30 21:16     ` Filip Navara
2005-07-30 21:28     ` Christian MICHON
2005-07-30 23:04       ` Steve D. Perkins
2005-07-30 23:04     ` Paul Brook
2005-07-30 23:16       ` Steve D. Perkins
2005-07-30 23:39         ` Paul Brook [this message]
2005-08-01 11:34           ` Gwenole Beauchesne

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=200507310039.59060.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=lists@steveperkins.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).