From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how people learn things (was architectures)
Date: Fri, 13 Jul 2001 18:20:22 +0200 [thread overview]
Message-ID: <20010713182020.C22003@cackle.proxima.alt.za> (raw)
In-Reply-To: <3B4F091E.9242B958@null.net>; from Douglas A. Gwyn on Fri, Jul 13, 2001 at 03:26:08PM +0000
On Fri, Jul 13, 2001 at 03:26:08PM +0000, Douglas A. Gwyn wrote:
>
> Lucio De Re wrote:
> > No more than from Intel (they are to be blamed for CP/M, too),
> > overlooking the fact that their address bus was wider than the
> > register size, or scrapping the i860/i960 developments.
> > They are rushed decisions that can't be reversed. ...
>
> Even the original PDP-11 had a wider address bus than its
> register (word) size. It wasn't a "rushed decision", although
> in the long run it caused enough trouble that a whole new
> architecture was designed to replace it.
Do you mean to tell me that DEC had a segmented architecture, with
haphazard default "base" registers, a LOCK instruction to lock the
bus for the following fetch cycle (whatever for? even the Univac
1106 had the more sane test-and-set) and a faulty MOV SS,XX that
did _not_ lock the bus for the following MOV SP,YY as was the
intention?
I bet the 20-bit address was an oversight, one that is still being
dragged along in this era of 64-bit registers. For heaven's sake,
Intel's marketing hype was full of praise for the ability to have
2^12 (overlapping) segments, and to this day the Pentium has segment
registers. Worse, one reads of superservers addressing up to
64Gigabytes of main memory - must be programmed in assembler 'cause
it's a long time since I've seen a compiler capable of producing
segmented architecture code.
> architecture was designed to replace it.
No, not to "replace it", but to propagate it.
++L
next prev parent reply other threads:[~2001-07-13 16:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 9:12 okamoto
2001-07-13 10:07 ` Boyd Roberts
2001-07-13 10:49 ` Lucio De Re
2001-07-13 10:59 ` Boyd Roberts
2001-07-13 11:11 ` Lucio De Re
2001-07-13 15:26 ` Douglas A. Gwyn
2001-07-13 16:20 ` Lucio De Re [this message]
2001-07-14 0:28 ` Boyd Roberts
2001-07-16 8:54 ` Douglas A. Gwyn
2001-07-16 9:55 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 18:15 David Gordon Hogan
2001-07-16 16:21 rog
2001-07-16 16:46 ` suspect
2001-07-13 16:32 jmk
2001-07-16 8:55 ` Douglas A. Gwyn
2001-07-16 15:21 ` Rick Hohensee
2001-07-13 16:22 rog
2001-07-14 0:23 ` Boyd Roberts
2001-07-16 8:54 ` Douglas A. Gwyn
2001-07-16 15:46 ` david presotto
2001-07-13 12:49 presotto
2001-07-13 13:38 ` Boyd Roberts
2001-07-13 15:44 ` Douglas A. Gwyn
2001-07-14 0:19 ` Boyd Roberts
2001-08-02 10:27 ` Ralph
2001-08-02 11:24 ` Boyd Roberts
2001-08-03 9:05 ` Ralph Corderoy
2001-08-03 10:15 ` Boyd Roberts
2001-07-13 9:17 okamoto
2001-07-13 8:00 Laura Creighton
2001-07-13 9:48 ` Boyd Roberts
2001-07-13 15:25 ` Douglas A. Gwyn
2001-07-13 15:44 ` Boyd Roberts
2001-07-13 20:47 ` Steve Kilbane
2001-07-14 14:45 ` Boyd Roberts
2001-07-13 15:25 ` Douglas A. Gwyn
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=20010713182020.C22003@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).