The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] PDP-11 questions
Date: Mon, 25 Jan 2016 04:07:16 +0100	[thread overview]
Message-ID: <56A59164.2030806@update.uu.se> (raw)
In-Reply-To: <mailman.29.1453684304.15972.tuhs@minnie.tuhs.org>

On 2016-01-25 02:11, jnc at mercury.lcs.mit.edu  (Noel Chiappa) wrote:
>
>      > The later M9301 (see disassembly of the contents here:
>      >http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/M9301-YA.mac
>      > of one variant) didn't clear memory either
>
> OK, so_my_  memory is failing! That code does in fact test the memory.
>
> (Although, looking at it, I can't understand how it works; after writing the
> contents of R3 into the memory section it it asked to test, it complements the
> test value in R3, before comparing it with the memory it just wrote with R3,
> to make sure they are the same. Maybe there's an error in the dis-assembly?)

Read the code again, you missed it. :-)
The code first writes one value into memory (R3), then complements R3, 
and for each location checks that the memory is *not* equal to R3, and 
then writes R3 and checks that it now matches. Essentially checking that 
it can be changed into a wanted value in time. And it does it two times. 
First zeroing, and then writing ones, and then back to zeroes again, so 
yes, the memory will be left containing all zeros, except for what 
memory isn't tested.

> Anyway, it should have left the memory mostly containing all 0's.

Indeed.

	Johnny

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt at softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol


       reply	other threads:[~2016-01-25  3:07 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.29.1453684304.15972.tuhs@minnie.tuhs.org>
2016-01-25  3:07 ` Johnny Billquist [this message]
2016-01-25  3:09 ` Johnny Billquist
2016-01-25 12:54   ` John Cowan
2016-01-25 13:09     ` Johnny Billquist
2016-01-25 13:49     ` Johnny Billquist
2016-01-25 16:00       ` John Cowan
2016-01-25 16:17         ` Johnny Billquist
2016-01-25 16:43           ` John Cowan
2016-01-26 20:07 Doug McIlroy
2016-01-26 20:44 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2016-01-26 19:36 Doug McIlroy
2016-01-26 19:59 ` Warren Toomey
2016-01-25  1:11 Noel Chiappa
2016-01-25  1:30 ` Clem cole
2016-01-24 22:40 Norman Wilson
2016-01-25  1:55 ` David Ritchie
2016-01-25  1:59   ` Ronald Natalie
2016-01-25  2:14   ` Clem cole
2016-01-25 11:29 ` Tony Finch
2016-01-25 13:25   ` Ronald Natalie
2016-01-25 16:18   ` Pete Turnbull
2016-01-25 19:37     ` Clem Cole
2016-01-24 22:40 Norman Wilson
2016-01-25  0:23 ` Ronald Natalie
2016-01-24 18:56 Noel Chiappa
     [not found] <mailman.25.1453658502.15972.tuhs@minnie.tuhs.org>
2016-01-24 18:34 ` Johnny Billquist
2016-01-24 18:30 Noel Chiappa
2016-01-24 18:36 ` Ronald Natalie
2016-01-24 21:10   ` John Cowan
2016-01-25  0:11 ` scj
2016-01-25  0:36   ` Clem cole
2016-01-24 18:01 Noel Chiappa
2016-01-24 17:37 Mark Longridge
2016-01-24 18:49 ` Clem Cole
2016-01-25  3:16   ` Dave Horsfall
2016-01-25  5:32     ` Warren Toomey
2016-01-25 12:27       ` Clem cole
2016-01-25 13:38         ` Lawrence Stewart
2016-01-25 14:15           ` Clem Cole
2016-01-26 19:52         ` Dave Horsfall
2016-01-26 20:41           ` Clem Cole

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=56A59164.2030806@update.uu.se \
    --to=bqt@update.uu.se \
    /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).