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 <v0vuqo$12om$1@gal.iecc.com>
Deutsch   English   Français   Italiano  
<v0vuqo$12om$1@gal.iecc.com>

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

Path: ...!weretis.net!feeder9.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!not-for-mail
From: John Levine <johnl@taugh.com>
Newsgroups: comp.arch
Subject: Re: Byte Addressability And Beyond
Date: Thu, 2 May 2024 11:52:56 -0000 (UTC)
Organization: Taughannock Networks
Message-ID: <v0vuqo$12om$1@gal.iecc.com>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 2 May 2024 11:52:56 -0000 (UTC)
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970";
	logging-data="35606"; mail-complaints-to="abuse@iecc.com"
In-Reply-To: <v0s17o$2okf4$2@dont-email.me> <v0uihh$3e0vg$5@dont-email.me> <v0upm3$idk$1@gal.iecc.com> <v0v93c$3m7rm$2@dont-email.me>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Bytes: 2073
Lines: 28

According to Lawrence D'Oliveiro  <ldo@nz.invalid>:
>Sure. 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”?

You really should stop guessing about computer architectures rather
than reading up on them.

On S/360, which is the ur-big-endian machine, memory to memory moves
are different from register loads and stores.  There are ICM and STCM
instructions that take a four bit mask to say which bytes in the
register to load or store.  There are also IC and STC for the common
case that you only want to load or store the low byte.

>In other words, even on big-endian architectures, registers are still 
>interpreted as little-endian!
>
>Isn’t that fun?

I suppose it would be if it were true.


-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly