From: Duraid Madina <duraid@octopus.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Itanium gets supercomputing software
Date: Fri, 11 Apr 2003 20:49:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705475@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705464@msgid-missing>
I guess I was being a bit subtle.
I'm well aware there are things you can do with a simulator that you
can't do with hardware. Like test your code against what's supposed to
happen, not what actually happens. ;)
My point wasn't that software simulators are useless, but that software
simulators _should_ be useless **4 years** (!!) after the public
availability of hardware.
When I said:
> I put it to you that software is easier to develop on hardware.
I meant that at this late stage, one would expect that people would be
writing software, on their hardware. And not a whole lot else, all
things considered. Do you see x86 linux people using simulators? Once in
a blue moon, perhaps. Does anyone doubt that the x86-64 port will mature
a heck of a lot faster than linux-ia64 has? One doesn't need to think
for very long to realise why this might be.
Don't get me wrong, I think Linus was being a complete idiot for his
comments against IA64 and for x86-64, but insofar as keeping hardware
pricing so high that Joe K. Hacker can't even dream of affording it is
"good business" on Intel/HP's part, it's an even better way of keeping
your kernel untested.
Duraid
David Kågedal wrote:
> Exactly. There are a lot of things that you can do with a simulator
> that you can't do with hardware. Developing software before hardware
> is available is just one of them. (plug mode on) That's why we sell
> simulators for most major current CPU architectures. Including IA64.
next prev parent reply other threads:[~2003-04-11 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 7:51 [Linux-ia64] Re: Itanium gets supercomputing software David Kågedal
2003-04-11 20:49 ` Duraid Madina [this message]
2003-04-11 22:08 ` David Mosberger
2003-04-11 22:54 ` Duraid Madina
2003-04-11 23:05 ` David Mosberger
2003-04-12 15:50 ` David Kågedal
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=marc-linux-ia64-105590723705475@msgid-missing \
--to=duraid@octopus.com.au \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.