From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EOfeR-00070V-Nv for qemu-devel@nongnu.org; Sun, 09 Oct 2005 14:11:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EOfeQ-000707-Qt for qemu-devel@nongnu.org; Sun, 09 Oct 2005 14:11:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EOfeQ-000704-Ng for qemu-devel@nongnu.org; Sun, 09 Oct 2005 14:11:58 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1EOfeQ-0006cA-Gd for qemu-devel@nongnu.org; Sun, 09 Oct 2005 14:11:58 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EOfdD-00033H-0L for qemu-devel@nongnu.org; Sun, 09 Oct 2005 20:10:43 +0200 Received: from dialup-4.255.74.86.dial1.seattle1.level3.net ([4.255.74.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Oct 2005 20:10:42 +0200 Received: from michel by dialup-4.255.74.86.dial1.seattle1.level3.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Oct 2005 20:10:42 +0200 From: Michel Pelletier Date: Sun, 09 Oct 2005 10:54:47 -0700 Message-ID: <43495967.4050608@cignex.com> References: <433D60D0.8040601@bacbuc.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <433D60D0.8040601@bacbuc.dyndns.org> Sender: news Subject: [Qemu-devel] Re: Current state of GCC 4 (non-)"support" on x86-64 ? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org A copule others on this thread mentioned that you can compile the kqemu module with gcc 4 and the rest of qemu with gcc 3.x. Did this work for you? Did it create a performance boost? I'm asking because I just got qemu working on my ubuntu AMD64 and it took me a bit of tinkering to figure out the gcc 4/3.4 issue. Eventually I compiled it all, including kqemu, with gcc 3.4 and it all works great! The 3.4 compiled kernel module worked fine with the 4 compiled kernel. QEMU is really fast! I fooled one of my friend into thinking that I was actually running a native windows XP. Is it that much more worth it to complile kqemu with gcc 4? Thank you QEMU developers! I'm keeping QEMU under my tool belt from now on. Something I'd like to research, is there any possibility, or has anyone else considered the possibility to do 1280x800 widescreen (or other widescreen resolutions)? -Michel Emmanuel Charpentier wrote: > Dear list, > > I understand that the current "official" qemu needs gcc 3.x and won't > compile with gcc 4.x > > I also understand that using a gcc3-compiled module (kqemu, in the > present case) entails a cgg3-compiled kernel. > > I successfully recompiled such a kernel and qemu. So far so good. > > However, this annoys me : the distribution I use (Ubuntu amd64) has > switched (foolishly, IMHO) to gcc 4 for its' "native" kernels ... and > proprietary kernel modules packages. > > Since using those proprietary modules (for video, etc ...) give a *huge* > performance boost to my poor laptop, I'd rather use them for the time > being. And since rebuilding those packages is (apparently) a $h!+load of > work, I'd rather patch qemu sources and use a "native" kernel... > > Paul Brooks posted on May 12 a patch allowing compilation of qemu on a > X86-64 host with GCC4. However, he didn't mention the use of gcc 4 for > kqemu generation. > > So the question is : > Does Pa ul's patch allow for successful compilation of qemu and kqemu > with GCC 4, at least on X86-64 ? > > Thank you for your answers and comments ! > > Emmanuel Charpentier