From: nao@tom-yam.or.jp (Naoki Hamada)
Subject: [TUHS] Query on PDP-11 assembly
Date: Wed, 30 Apr 2008 23:41:17 +0900 [thread overview]
Message-ID: <2da2ec620804300741i1bd39a48lf5b5ba09830793b4@mail.gmail.com> (raw)
In-Reply-To: <48187A41.80105@coraid.com>
Hi,
This technique was a very common one in assembler sources for PDP-11
versions of UNIX. For example, m40.s of Version 6 UNIX shows a line
"jsr r0,call1; _trap" in its trap routine. I feel very funny to
tell this to Warren, the author of apout!
Anyway, it could be a source of the null-terminated expression of
character strings of the C language, I guess.
Naoki Hamada
nao at tom-yam.or.jp
next prev parent reply other threads:[~2008-04-30 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:56 Warren Toomey
2008-04-30 13:55 ` Brantley Coile
2008-04-30 14:41 ` Naoki Hamada [this message]
2008-05-01 23:47 ` Warren Toomey
2008-04-30 16:53 ` Milo Velimirovic
2008-04-30 17:00 ` Larry McVoy
2008-04-30 17:47 ` John Cowan
2008-04-30 17:59 ` Larry McVoy
2008-04-30 15:08 ` Carl Lowenstein
2008-04-30 16:20 James A. Markevitch
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=2da2ec620804300741i1bd39a48lf5b5ba09830793b4@mail.gmail.com \
--to=nao@tom-yam.or.jp \
/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).