From: "Jim C. Brown" <jma5@umd.edu>
To: Leonard paniq Ritter <paniq@paniq.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 0.7.2 and gcc 4
Date: Sat, 29 Oct 2005 13:10:37 -0400 [thread overview]
Message-ID: <20051029171037.GA7447@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1130600389.6060.10.camel@zeitgeist>
On Sat, Oct 29, 2005 at 05:39:48PM +0200, Leonard paniq Ritter wrote:
>
> hm i see. well, when will gcc 4 be working with qemu? i'm asking because
> my distribution switched to gcc 4 a while ago.
>
A patch is already available, as noted below.
My understanding of the register allocation problem is that it is technically
a bug of gcc, not qemu. So can't say when it will be fixed.
A long term solution, called qops, that replaces the part of qemu that is gcc3
dependant, called dyngen, is in the works. This does not have the register allocation
issue that the gcc 4 patch has, but is not complete yet. (Feel free to help out!)
In any case, most distros allow one to use gcc33 or something to compile
programs. I think a 'make CC=gcc33' would do the trick, if you have that
compiler installed.
> On Tue, 2005-10-25 at 20:50 -0400, Jim C. Brown wrote:
> > Yes, but I caution you before using it. You shouldn't use the patch unless you
> > know what you are doing, and why you have to do it.
> >
> > Also keep in mind that even with the patch, qemu doesn't always compile.
> > x86 guests on x86 hosts don't work because of another bug that causes
> > gcc to run out of registers, so it still won't compile. x86 guests on
> > x86_64 hosts (e.g. amd64 cpus running in 64bit mode) do work, though, and
> > I'd imagine that x86 guests on ppc hosts work as well.
> >
> --
> -- leonard "paniq" ritter
> -- http://www.mjoo.org
> -- http://www.paniq.org
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-10-29 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 21:46 [Qemu-devel] qemu 0.7.2 and gcc 4 Leonard "paniq" Ritter
2005-10-26 0:50 ` Jim C. Brown
2005-10-29 15:39 ` Leonard "paniq" Ritter
2005-10-29 17:10 ` Jim C. Brown [this message]
2005-10-29 23:05 ` Leonard "paniq" Ritter
2005-10-30 0:20 ` Jim C. Brown
2005-10-30 1:03 ` Leonard "paniq" Ritter
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=20051029171037.GA7447@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=paniq@paniq.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).