From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: A Census of /etc and /sys Prior to V4
Date: Sat, 20 May 2023 04:13:12 +0000 [thread overview]
Message-ID: <9aOA0GH7FSvgFIs5EWZeEQqoCTKik2hOJYH0P14ddgDPiUUAqSe0MmATyey9D7Tqm6XTfvlsCxJNvZn-kukgp18V8EentRXWTs9jgLJRyIk=@protonmail.com> (raw)
In-Reply-To: <20230520020457.BA28718C074@mercury.lcs.mit.edu>
> > ac and mq EAE registers are still in use in s2-bits binaries
> > but have been replaced by s1-bits.
>
> Interesting. How did you work that out, BTW?
Regarding the EAE registers, in as19.s[1], there is this set of mappings:
012717;000000;01;177570 /csw
015176;000000;01;177300 /div
003270;000000;01;177302 /ac
051750;000000;01;177304 /mq
052224;000000;01;177306 /mul
073470;000000;01;177310 /sc
074620;000000;01;177311 /sr
054752;000000;01;177312 /nor
047000;000000;01;177314 /lsh
004500;000000;01;177316 /ash
Among others, here we have the mappings for ac, mq, mul, and div.
In the disassembled source of df(I) from s2-bits[2], at the second 9 label, ac, mq, div, and mul are used to perform a division by 10 (I think, my PDP-11-fu isn't *that* strong yet):
9:
clr ac
mov $10.,div
mov ac,-(sp)
tst mq
beq 2f
jsr pc,9b
In the disassembler output (I used pdp11dasm[3]) these values were all the same addresses as the above table from as(I).
In the source df.s under the V2/cmd section[4], this is instead replaced by use of the dvd opcode:
9:
clr r2
dvd $10.,r2
mov r3,-(sp)
mov r2,r3
beq 2f
jsr pc,9b
I've seen this sort of thing consistently as I comb through files in s2-bits, using stuff from s1-bits and V5 as references.
[1] - https://www.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/as19.s
[2] - https://gitlab.com/segaloco/v2src/-/raw/master/cmd/df.s
[3] - https://github.com/caldwell/pdp11dasm
[4] - https://www.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/df.s
- Matt G.
next prev parent reply other threads:[~2023-05-20 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 2:04 Noel Chiappa
2023-05-20 4:13 ` segaloco via TUHS [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 14:36 Noel Chiappa
2023-05-19 15:15 ` segaloco via TUHS
2023-05-15 4:27 [TUHS] " segaloco via TUHS
2023-05-15 12:19 ` [TUHS] " 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='9aOA0GH7FSvgFIs5EWZeEQqoCTKik2hOJYH0P14ddgDPiUUAqSe0MmATyey9D7Tqm6XTfvlsCxJNvZn-kukgp18V8EentRXWTs9jgLJRyIk=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.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).