qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Current state of GCC 4 (non-)"support" on x86-64 ?
Date: Fri, 30 Sep 2005 17:59:12 +0200	[thread overview]
Message-ID: <433D60D0.8040601@bacbuc.dyndns.org> (raw)

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

             reply	other threads:[~2005-09-30 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 15:59 Emmanuel Charpentier [this message]
2005-09-30 16:18 ` [Qemu-devel] Current state of GCC 4 (non-)"support" on x86-64 ? Paul Brook
2005-09-30 18:40   ` Jim C. Brown
2005-09-30 21:30 ` Henrik Nordstrom
2005-10-09 17:54 ` [Qemu-devel] " Michel Pelletier
2005-10-10  8:55   ` 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=433D60D0.8040601@bacbuc.dyndns.org \
    --to=charpent@bacbuc.dyndns.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).