From: Karl Magdsick <kmagnum@gmail.com>
To: qemu-devel@nongnu.org, calexicoz@gmail.com
Subject: Re: [Qemu-devel] Bug report
Date: Tue, 1 Nov 2005 19:00:46 -0500 [thread overview]
Message-ID: <cd8ecdef0511011600y7260f308u1da5cc6421f9747a@mail.gmail.com> (raw)
In-Reply-To: <e1843770511011548w26a3a3d2g32e47a24de4ab941@mail.gmail.com>
gcc 4.x is known not to compile qemu, due to a register allocation bug in gcc.
Also, the current qemu code generator is an ugly hack that relies on some
specifics of gcc 3.x function implementation. There is work being done
on a _real_ code generator for qemu.
-Karl
On 11/1/05, Julien Lancien <calexicoz@gmail.com> wrote:
> Hi,
>
> I am unable to compile qemu on my machine :p. I've attached the result
> of the configure and make.
>
> My gcc version is: 4.0.3 20051006 and kernel 2.6.13 vanilla.
>
> I used the CVS snapshot, but I got mostly the same problem with the
> 0.7.2 version.
> Tell me if you want more infos, and thanks for any help.
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
>
next prev parent reply other threads:[~2005-11-02 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 23:48 [Qemu-devel] Bug report Julien Lancien
2005-11-01 23:57 ` Mike Kronenberg
2005-11-02 0:00 ` Karl Magdsick [this message]
[not found] ` <e1843770511011607m1cda6256o37102cf17cc75fea@mail.gmail.com>
2005-11-02 0:08 ` Julien Lancien
2005-11-02 0:42 ` Jim C. Brown
2005-11-02 0:20 ` Philip Machanick
2005-11-02 7:03 ` Gwenole Beauchesne
-- strict thread matches above, loose matches on Subject: below --
2013-10-06 16:55 [Qemu-devel] bug report Peter Cheung
2009-01-11 12:07 Artem Kozarezov
2007-12-17 13:48 [Qemu-devel] Bug report Bas Wijnen
2007-12-18 16:52 ` Paul Brook
2007-12-19 1:11 ` Bas Wijnen
2006-12-03 16:40 Mike Smith
2004-04-11 15:04 J. Mayer
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=cd8ecdef0511011600y7260f308u1da5cc6421f9747a@mail.gmail.com \
--to=kmagnum@gmail.com \
--cc=calexicoz@gmail.com \
--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).