qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Orgis <thomas-forum@orgis.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: Latest SVN fails to build on Fedora Core 6 (same with 0.9.0)
Date: Thu, 29 Mar 2007 12:55:54 +0200	[thread overview]
Message-ID: <20070329125554.02174819@neuling> (raw)
In-Reply-To: <200703281556.59315.rob@landley.net>

Am Wed, 28 Mar 2007 15:56:59 -0400
schrieb Rob Landley <rob@landley.net>: 

> On Saturday 24 March 2007 8:32 am, Sunil Amitkumar Janki wrote:
> > Anyhow, I expect 32-bit hardware to gradually die because of wear and 
> > tear in the next few years and the replacement will be 64-bit hardware so
> > the problem will solve itself that way.
> 
> Specifically, in 2008 32-bit x86 hardware both drops below 50% of the 
> installed base and stops being a commercial viable option for new sales in 
> the desktop or laptop space.

Sure, 32bit is vanishing from new hardware sales.
But I got my first machine that is able to decentnly run qemu just half a year ago:
A used ThinkPad. I didn't buy a new computer system since my very first system
in 1995 (which had to return to shop because they put a broken video card in...
grmbl).
So for me, 32 bits are the state-of-the art, apart from my two machines at work,
which are Compaq XP1000's being 64 bit all-over, but as astonishing an
EV67@667Mhz still can be at crunching floating point numbers, it's not a host
for qemu VMs (esp. since it cannot use kqemu to accelerate x86 code ... hm,
would qemu/kqemu work to run Tru64 accelerated in a vm on alpha?;-).

And... I don't expect the 32bit hardware to die because of "wear and tear",
especially when thinking of the i486DX4 that handles my DSL NAT routing needs,
or about the Pentium 100 serving as music jukebox;-)
Not to forget a i386DX40 that still just works fine when I decide to power it up.

Well, I don't intend to run qemu on these old systems, and I only do it casually
on my ThinkPad to test some software under a different OS.
Sure, if becoming a qemu power user with several VMs doing work and
compiling stuff, I'd think about becoming a dual/quad AMD64 user.

On that edge, though, qemu should find a way to arrange with current
gcc versions... gcc3.4 won't hold forever.


Thomas.

  reply	other threads:[~2007-03-29 10:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17 13:37 [Qemu-devel] Latest SVN fails to build on Fedora Core 6 (same with 0.9.0) Thomas Orgis
2007-03-18  4:45 ` Tony Nelson
2007-03-18  8:37   ` Thomas Orgis
2007-03-18  9:18     ` Nigel Horne
2007-03-22 19:46       ` [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: " Thomas Orgis
2007-03-22 20:13         ` Sunil Amitkumar Janki
2007-03-23  9:58           ` Thomas Orgis
2007-03-23 10:21             ` Sunil Amitkumar Janki
2007-03-23 15:45               ` Paul Brook
2007-03-23 20:11                 ` Thomas Orgis
2007-03-24 12:32                   ` Sunil Amitkumar Janki
2007-03-24 12:55                     ` Julian Seward
2007-03-26  9:34                       ` Thomas Orgis
2007-03-28 19:56                     ` Rob Landley
2007-03-29 10:55                       ` Thomas Orgis [this message]
2007-03-29 14:55                         ` [Qemu-devel] QEMU Alpha target Stuart Brady
2007-03-29 15:08                           ` Paul Brook
2007-03-29 15:12                             ` Stuart Brady
2007-03-29 15:25                               ` Paul Brook
2007-03-29 21:01                                 ` J. Mayer
2007-03-29 15:25                         ` [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: Latest SVN fails to build on Fedora Core 6 (same with 0.9.0) Sunil Amitkumar Janki
2007-03-29 16:08                           ` Stuart Brady
2007-03-29 19:57                             ` J. Mayer
2007-03-29 20:04                               ` Brian Wheeler
2007-03-29 21:18                               ` [Qemu-devel] QEMU Alpha target Stuart Brady
2007-03-29 21:31                                 ` J. Mayer
2007-03-29 21:57                                   ` Stuart Brady
2007-03-29 21:48                                 ` Thomas Orgis

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=20070329125554.02174819@neuling \
    --to=thomas-forum@orgis.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).