Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Why did Motorola fail?
Date: Fri, 10 Aug 2018 11:13:48 -0400	[thread overview]
Message-ID: <CAC20D2NtaRuBbZOJgAdC3VT4VDhaCa-xNrES6Pu4GWGj0uP38Q@mail.gmail.com> (raw)
In-Reply-To: <20180810144320.GA17564@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]

On Fri, Aug 10, 2018 at 10:43 AM, Larry McVoy <lm at mcvoy.com> wrote:

> The original SPARC CPU was 20K gates and was faster than the 68020.
>
Yep...   pretty clean design.



> My guess is cheaper as well.

Maybe -- TI was the fab right?   Moto's fabs were pretty good, not as good
at Intel in those days.

IIRC TI was still transitioning from BiPolar to CMOS, and most of the fab
capacity was still in their BiPolar area (somewhere along the line the
bought Nat Semi).   As I understand from a buddy who as at TI at the time,
DSPs and SPARCs were driving the transistion.  But they might not have been
there yet.




> I was at Sun as they were making the
> transition from 68K to SPARC and we all fought to get SPARC machines
> because of performance.
>
Yeah, they kicked butt.  Less is more and all that.   Had us worried at
Stellar because we were doing custom (Gate Arrays).    We had hit 22 MIPS,
if I recall Sparc was 4-6 range; but that was pretty darned good for a
single chip at the time.



>
> I liked the 68K well enough, it was fairly nice in assembler (though
> my heart belongs to the PDP-11 first, the National 32032 next, and
> then the 68K for assembler).  But the SPARC chips were just faster.

+1

althought I'd probably swap the 68K and 32032 because the National device
(which was pretty much a vax on a chip, as the 68k was an 11 on a chip),
was clean and cool, it was later in my life; so I knew the 68K better.

BTW:  Stellar was a 'RISCy' 68K with support for Fortran (*i.e.*
indirection beyond pure load/store).   We used to say all devices post
Dave's papers were RISC ;-)    FWIW:
I never really thought much of the RISC chips, accept maybe the by the time
of the MIPS 4400 series; but then again they were were designed for
compiler writers.



And the whole RISC thing was a bit of marketing.   John Coche never said
"reduce to the instruction set", he said "compile to (*i.e.* expose) the
microcode."   Dave sort of missunderstood his message.

Clem
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20180810/a4387a9a/attachment.html>


  reply	other threads:[~2018-08-10 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  2:23 grog
2018-08-10  2:55 ` stewart
2018-08-10  6:00 ` arno.griffioen
2018-08-10  7:24 ` dave
2018-08-10  7:44 ` bakul
2018-08-10 13:40   ` clemc
2018-08-10 14:43 ` lm
2018-08-10 15:13   ` clemc [this message]
2018-08-10 15:45     ` lm
2018-08-10 15:53       ` [COFF] Why did Motorola fail? (Cost and performance) david

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=CAC20D2NtaRuBbZOJgAdC3VT4VDhaCa-xNrES6Pu4GWGj0uP38Q@mail.gmail.com \
    --to=coff@minnie.tuhs.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).