The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Bryan Cantrill on bfs & ta
Date: Fri, 19 Oct 2012 15:44:27 -0500	[thread overview]
Message-ID: <F4B07803-8CC0-4EF8-9668-878B4CAE0B0E@ccc.com> (raw)
In-Reply-To: <20121018234041.GB96785@eureka.lemis.com>

Greg

the 68000 and 68010 were 16 bit internals. ie a 16 bit barrel shifter and it took 2 ticks to perform 32 bit ops.    a natural int was indeed 16 bits in the base registers although they also could be used as 32 bit registers (2 ticks ) so some 68k compilers defined int as 16 others as 32 (more in a minute). it technically was LP32 not ILP32

the external logic (ie pins) supported 24 bits of address.   moto fortunately passed all 32 bits along on the first chip and onto storage (thank you Les & Nick) so when later versions had a full  32 bit shifter everything just worked.  this meant that both chips supported 32bit addressing.  So while the machine operated 16 bits at a time the programmer had a full 32 bit view (and eventually a 32 bit virtual address space) even though the chip only supported 24 bits of address and operated 16 bits of data at a time. 


They're so even thought they were 16 bit internally.  I'd never think of either chop as a 16 bit machine

as for 16/32 bit argument - the hacked C compiler that Glasser and I cobbled together in 1979 at Tektronix used 16 bit.   IIRC the rts guys (jack test et al) used 32 bits at day one even though the natural int was 16 bits. 



there were advantages to both solutions and Jeff Mogul and i used argue about.  looking back on the 68000 in hind sight MIT got it right and while it worked mildly faster a 16 bit int was a bad idea

Clem

PS but I agree.  SunOS never ran on a pure 16 not machine.  on fact they started with compiler derived from Test et al.  



PPS. we relived this whole argument with 64 bits and it was interesting that we generally came to think LP64 made more sense for chips like Alpha

On Oct 18, 2012, at 6:40 PM, Greg 'groggy' Lehey <grog at lemis.com> wrote:

> On Thursday, 18 October 2012 at 23:51:20 +0100, Sevan / Venture37 wrote:
>> http://www.youtube.com/watch?v=Rk8aZv0JJuk&feature=player_detailpage#t=3493s
>> 
>> "SunOS has never run on a 16bit machine"
>> 
>> My response was M68000 & 386 but his counter response was they both
>> supported 32bit addressing.
> 
> They're also 32 bit internally.  I'd never think of either as a 16 bit
> machine.
> 
> Greg
> --
> Sent from my desktop computer.
> Finger grog at FreeBSD.org for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed.  If your Microsoft MUA reports
> problems, please read http://tinyurl.com/broken-mua
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs



  reply	other threads:[~2012-10-19 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 22:51 Sevan / Venture37
2012-10-18 23:40 ` Greg 'groggy' Lehey
2012-10-19 20:44   ` Clem Cole [this message]
2012-10-19 20:54     ` John Cowan
2012-10-19 22:13       ` Peter Jeremy
2012-10-22  0:33 ` Larry McVoy
2012-10-22 13:01   ` A. P. Garcia
2012-10-22 13:34     ` Larry McVoy
2012-10-22 14:05       ` A. P. Garcia
2012-10-22 14:13         ` Larry McVoy
2012-10-22 14:17           ` A. P. Garcia

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=F4B07803-8CC0-4EF8-9668-878B4CAE0B0E@ccc.com \
    --to=clemc@ccc.com \
    /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).