Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Byte Addressability And Beyond
Date: Sun, 5 May 2024 00:19:34 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <v16jam$1fjrg$1@dont-email.me>
References: <v0s17o$2okf4$2@dont-email.me> <v0uihh$3e0vg$5@dont-email.me>
	<v0upm3$idk$1@gal.iecc.com> <v0v93c$3m7rm$2@dont-email.me>
	<v0vuqo$12om$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 05 May 2024 02:19:34 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="33a041cd80492abf930d5e0c5f5526b9";
	logging-data="1560432"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19MA3MMyFfrp3D/b/IUiGe8"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:STWEt+agqW6EsfLUFc0wdODnc2Y=
Bytes: 1707

On Thu, 2 May 2024 11:52:56 -0000 (UTC), John Levine wrote:

> According to Lawrence D'Oliveiro  <ldo@nz.invalid>:
>
>> Consider this pseudo-assembly-language sequence:
>>
>>    move.l a, b
>>    move.b b, c
>> ...
>> Now the question is: which byte from “a” ends up at location “c”?
> 
> On S/360, which is the ur-big-endian machine, memory to memory moves are
> different from register loads and stores.

Hint: in the register-memory-register case, you would do an MVC followed 
by LOAD. In the memory-register-memory case, it would be LOAD followed by 
MVC.

Does that put it in System/360 terms you can understand?