From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] asm helper routines in v7
Date: Wed, 5 Jan 2022 22:26:09 -0500 [thread overview]
Message-ID: <CAKH6PiXJXGFncLroNX_wNW2--7mVDYrVHfZZY9_SKXHzHEP=fA@mail.gmail.com> (raw)
> It would be nice to hear about the rationale from a primary source.
Assembly language was deemed a last resort, especially as portability
was coming to the fore. As I wrote in A Research Unix Reader,
"Assembly language and magic constants gradually declined from the
status of the 'real truth' (v4) to utterly forgotten (v8)." In v7,
assembler usage was demoted to the bottom of syscall man pages. It
could also be found in /usr/src/libc/sys/*.s
Doug
next reply other threads:[~2022-01-06 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 3:26 Douglas McIlroy [this message]
2022-01-06 3:37 ` Warner Losh
2022-01-06 16:00 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2022-01-04 20:37 Will Senn
2022-01-04 21:12 ` Dan Cross
2022-01-04 21:24 ` Will Senn
2022-01-04 21:28 ` Warner Losh
2022-01-05 17:35 ` Dan Cross
2022-01-04 21:38 ` 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='CAKH6PiXJXGFncLroNX_wNW2--7mVDYrVHfZZY9_SKXHzHEP=fA@mail.gmail.com' \
--to=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@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).