Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Brett <ggtgp@yahoo.com>
Newsgroups: comp.arch
Subject: is Vax adressing sane today
Date: Thu, 5 Sep 2024 21:03:37 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <vbd6b9$g147$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 05 Sep 2024 23:03:37 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="b200fcf8ebfb9a06d94e90ad2ca6d720";
	logging-data="525447"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18+G0nA2FJyLqjXDLL1R9nW"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:rDsJyCJm5eMQx628CpKYFkCFPWo=
	sha1:0Qdg5QxwIcSHFw6aKIhiyB+xKBc=
Bytes: 1566



Is Vax addressing sane today?

I am not talking indirect addressing, that is stupid.

It has been determined from trusted sources that add from memory and add to
memory as used in x86 are sane, and not much of a problem.

But Vax allows all three arguments to be in memory with different pointers.

Is this sane, just a natural progression if you allow memory operands?

Packing three offsets in an instruction that can be decoded reasonably is a
whole other problem…

Heads and tails encoding could actually do this reasonably, and the code
density would be actually be better than most competitors. Heads and tails
is not that easy, but it’s not x86 difficult.