qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu vs gcc4
Date: Sun, 22 Oct 2006 21:27:08 -0400	[thread overview]
Message-ID: <200610222127.08346.rob@landley.net> (raw)
In-Reply-To: <45391B22.1050608@palmsource.com>

On Friday 20 October 2006 2:53 pm, K. Richard Pixley wrote:
> Could someone please explain the issue with gcc4, please?  Or point me 
> to an existing explanation?
> 
> I mean, I understand that qemu is believed to be building incorrectly 
> with gcc4.  But what is the failure mode folks have been seeing?  And 
> what's being done about it or what needs to be done about it?  Is this 
> an issue for all targets or is it x86 specific?

There's a patch to fix it in http://busybox.net/downloads/qemu (which works 
for 0.8.0 through 0.8.2, dunno about current cvs).  This is a collection of 
four different patches I got from a gentoo web page via google.

Basically, gcc changed in a way that broke qemu.  There's been an open bug 
report in gcc ever since, but the GCC developers really aren't interested in 
backwards compatability.  (Heck, gcc 4.0 breaks building bash 2.05b).  The 
qemu developers aren't interested in applying ugly patches to support gcc 4.x 
until gcc 3.x becomes so obsolete nobody ships it anymore.  (And considering 
that there are still some niche embedded boards that have hacked up versions 
of gcc 2.95 targeting them and nothing else, I wouldn't be surprised if in 
five years we have your main compiler and the compiler to build qemu, ala 
kgcc under Red Hat 7.  *shrug*)

I was pondered trying to get tcc to build qemu, and even made a mercurial copy 
of CVS and started collecting old patches from the list (since CVS hadn't had 
a single patch checked into it in eight months and there were other old 
patches from a full year ago which I needed to apply before the thing would 
work on Ubuntu 6.06).  But Fabrice showed back up on tuesday and checked in a 
patch, and now I've got a fork that's out of sync with mainline.  Since I 
have no desire to be in Fabrice's way if he still has any interest in the 
project, I've mothballed my fork and moved on to other things...

The current state of TCC trying to build qemu-0.8.2 is that it blows up on the 
very first file.  Just getting it to compile the full source (let alone 
actually work) seems like a significant undertaking, but I was trying it as a 
learning experience so who knows how much work it actually is.  Might be 
simple if you know what you're doing...

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery

  parent reply	other threads:[~2006-10-23  1:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:53 [Qemu-devel] qemu vs gcc4 K. Richard Pixley
2006-10-22 22:06 ` Johannes Schindelin
2006-10-23  8:16   ` Martin Guy
2006-10-23 12:20     ` Paul Brook
2006-10-23 13:59       ` Avi Kivity
2006-10-23 14:10         ` Paul Brook
2006-10-23 14:28           ` Avi Kivity
2006-10-23 14:31             ` Paul Brook
2006-10-23 14:35               ` Avi Kivity
2006-10-23 17:41     ` K. Richard Pixley
2006-10-23 17:58       ` Paul Brook
2006-10-23 18:04         ` K. Richard Pixley
2006-10-23 18:20           ` Laurent Desnogues
2006-10-23 18:37           ` Paul Brook
2006-10-24 23:39             ` Rob Landley
2006-10-25  0:24               ` Paul Brook
2006-10-25 19:39                 ` Rob Landley
2006-10-26 18:09                   ` Daniel Jacobowitz
2006-10-31 16:53             ` Rob Landley
2006-10-31 19:02               ` Paul Brook
2006-10-31 20:41                 ` Rob Landley
2006-10-31 22:08                   ` Paul Brook
2006-10-31 22:31                     ` Laurent Desnogues
2006-10-31 23:00                       ` Paul Brook
2006-11-01  0:00                     ` Rob Landley
2006-11-01  0:29                       ` Paul Brook
2006-11-01  1:51                         ` Rob Landley
2006-11-01  3:22                           ` Paul Brook
2006-11-01 16:34                             ` Rob Landley
2006-11-01 17:01                               ` Paul Brook
2006-10-31 23:17                 ` Rob Landley
2006-11-01  0:01                   ` Paul Brook
2006-10-30  4:35         ` Rob Landley
2006-10-30 14:56           ` Paul Brook
2006-10-30 16:31             ` Rob Landley
2006-10-30 16:50               ` Paul Brook
2006-10-30 22:54                 ` Stephen Torri
2006-10-30 23:13                   ` Paul Brook
2006-10-23  1:27 ` Rob Landley [this message]
2006-10-23  1:44   ` Paul Brook
2006-10-23  1:45   ` Johannes Schindelin
2006-10-23 17:53     ` K. Richard Pixley
2006-10-23 18:08     ` Rob Landley

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=200610222127.08346.rob@landley.net \
    --to=rob@landley.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).