On Sat, 21 Aug 1999 00:15:57 -0400, you wrote:
>>(No, I won't buy an assember. An assembLer, on the other hand ;-) )
>What month comes after Assember?
I think it's Dectembruary. (Or is that just on the Julian calendar?)
Foghorn Leghorn
[EMAIL PROTECTED]
__
>And gas, taking the bloatedness to new heights, will require 8 bytes of
>memory, 32 kB of hard disk space (making it impossible to compile Merced
>code on a C64 -- the gas team has already issued a public apology for this)
>and a toaster.
Gasp!
>(No, I won't buy an assember. An assembLer, on t
Dear All: I'm catching up on lots of postings, so forgive me if this
is long-winded.
Simon Burge writes:
>Compaq have a DS20 Alpha with 2 500MHz 21264 CPUs on the internet
>for people to try out.
This is a dual-CPU version of the same kind of machine (a.k.a. ev6
or 21264 - the naming profusion
Hi all,
I need your help. It takes just a few moments on your Windows computer.
I need test data from a broad variety of network connection and ISP types to see
if a new Internet connection detection method will work or supplement the RAS
method used in v16-v18 now.
There's a tiny Win32 consol
On Fri, Aug 20, 1999 at 04:45:36PM -0400, Marc Getty wrote:
>I can see it now! Microsoft Visual Assember++ it will require 2048 MB of RAM, 16
>GB of hard disk space, and an 8 GHz Merced processor. You know it's coming, you
>know you don't want it, and you know you will still buy it.
And gas, taki
> Seems like assemblers will have to get smarter in the future? Just the
> `simple' feature of being able to edit those 8 streams separate would
> appearently help a lot, and some visual cue on when an operation is
> finished would also be an idea. (Wonder why the last one hasn't been
> implemente
Hi,
For anyone interested, I've placed some more versions of MacLucasUNIX
on my ftp server (ftp://lettuce.edsc.ulst.ac.uk/gimps/software)
There are now additional versions compiled using gcc for Ultra CPUs
(the original file also worked on SuperSparcs) and three executables
compiled by Bill R
On Thu, Aug 19, 1999 at 05:39:59PM -0700, John R Pierce wrote:
>The assembler (micro?) coder had to
>keep track of which parts of what execution unit would take how long to do
>each instruction, and not rely on results before they were ready. To keep
>the machine actually humming along at even cl
> IA64 is really VLIW (very long instruction word), which is quite different
> than traditional sequential RISC. It requires the compiler to do a LOT of
> massively parallel pipeline scheduling to achieve optimal results. HP has
> a
> leg up on this compiler technology as IA64 is based on their
