From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [TUHS] UNIX/32V
Date: Sun, 19 Oct 2003 04:20:12 -0400 [thread overview]
Message-ID: <20031019082054.EB1A81E85@minnie.tuhs.org> (raw)
Wesley Parish:
I was wondering as well, are there any VAX assembler manuals online, in an
easily-copyable form?
I've encountered html ones, but that isn't quite what I mean.
What do you mean, then? In what way isn't HTML suitable?
I don't mean to be obstreperous; I just think it would be
easier to help if you made it clearer what you need and
what you don't.
To split hairs further, what do you mean by `VAX assembler
manual'? There's a paper named Assember Reference Manual
that came in Berkeley's Volume 2C for 3BSD, written by
Reiser (Bell Labs) and Henry (Berkeley); it is a compact
description of syntax and pseudo-ops, but doesn't list or
explain the VAX instruction set itself.
The best reference I know for the VAX instruction set is
the official DEC manual called VAX Architecture Reference
Manual (EK-VAXAR-RM), but at more than 500 pages it is not
easily-copyable even in the way we thought of copying when
it was published, i.e. that depicted on the cover of the
latter-day Lions book.
Norman Wilson
Toronto ON
next reply other threads:[~2003-10-19 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 8:20 Norman Wilson [this message]
2003-10-19 9:35 ` Wesley Parish
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 16:02 Carl Lowenstein
2003-10-18 9:19 nao
2003-10-18 16:21 ` Robert Brockway
2003-10-19 6:46 ` Wesley Parish
2003-10-19 6:55 ` Robert Brockway
2003-10-19 13:00 ` Kroumovi, Ivaylo & Mladena
2003-10-20 7:45 ` Wesley Parish
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=20031019082054.EB1A81E85@minnie.tuhs.org \
--to=norman@nose.cs.utoronto.ca \
/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).