Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <v16jem$1fjrg$2@dont-email.me>
Deutsch   English   Français   Italiano  
<v16jem$1fjrg$2@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

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:21:42 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <v16jem$1fjrg$2@dont-email.me>
References: <v0s17o$2okf4$2@dont-email.me> <v0uihh$3e0vg$5@dont-email.me>
	<9ef6b3ccf22295ffa50de9ec20623d92@www.novabbs.org>
	<v11u92$cghm$1@dont-email.me> <v13b6l$2uft$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:21:42 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="33a041cd80492abf930d5e0c5f5526b9";
	logging-data="1560432"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18yr3cBDlsf11MCAH3sNyeq"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:nyf5IwYqi6g8fIHrOHF3VoXJPQg=
Bytes: 1938

On Fri, 3 May 2024 18:42:29 -0000 (UTC), John Levine wrote:

>>> Lawrence D'Oliveiro wrote:
>>> 
>>>>     move.l a, b
>>>>     move.b b, c
> 
> Here's a concrete example on S/360.
> 
>    L    R,100
>    STH  R,200
> 
> That does a four byte load of location 100 into a register, and then a
> two byte halfword store into 200.  The load gets bytes 100 through 103
> with 100 going into the high byte of the register.  The store puts its
> values into bytes 200 and 201.  Since it's the low half of the register,
> the new contents of 200 and 201 are the old contents of 102 and 103.

So using the same register name to address a halfword gives you the low 
half of the register, not the high half?

Whereas using the same memory address to address a halfword gives you the 
high half of the word at that location, not the low half?