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 <6d6fa399e0f5dd481125348fa56d8ef8@www.novabbs.org>
Deutsch   English   Français   Italiano  
<6d6fa399e0f5dd481125348fa56d8ef8@www.novabbs.org>

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

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mitchalsup@aol.com (MitchAlsup1)
Newsgroups: comp.arch
Subject: Re: why bits, Byte Addressability And Beyond
Date: Tue, 7 May 2024 00:57:00 +0000
Organization: Rocksolid Light
Message-ID: <6d6fa399e0f5dd481125348fa56d8ef8@www.novabbs.org>
References: <v0s17o$2okf4$2@dont-email.me> <v19f9u$2asct$1@dont-email.me> <v19goj$h9f$1@gal.iecc.com> <5r3i3j58je3e7q9j2lir1gd4ascsmumca2@4ax.com> <v1bgru$jo2$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="312097"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A";
User-Agent: Rocksolid Light
X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Site: $2y$10$zb7auPyhzKbTSVubqbZ3fev.qIA9W/ffhNvVwQskv/ObuNsKmaMGq
Bytes: 2303
Lines: 28

John Levine wrote:

> According to John Savard  <quadibloc@servername.invalid>:
>>On Mon, 6 May 2024 02:54:11 -0000 (UTC), John Levine <johnl@taugh.com>
>>wrote:
>>
>>>Why do you think bit addressing will be
>>>faster than shifting and masking? ...

>>So just because a processor has a 64-bit bus to memory doesn't mean it
>>has to implement fetching a single byte from memory by doing a shift
>>and mask operation in a 64-bit register. Instead, each byte of the bus
>>could have a direct wired path to the low 8-bits of the internal data
>>bus feeding the registers.

> I was more thinking about storing bit fields, where you probably have
> to fetch the whole word or cache line or whatever, shift the new field
> into it, and then store it back. You already have to do something like
> that for byte stores but bit addressing makes it 8 times as hairy.

Which is no different than ECC, BTW...

Could someone invent a bit field ISA that was as efficient as a byte
accessible architecture:: probably.

Could this bit accessible architecture outperform a byte ISA on
typical codes:: doubtful. Two reasons:: 1) more delay in the 
LD/ST pipeline, 2) most programs use as little bit-fielding as
possible (not as much as practical) !!!