Deutsch   English   Français   Italiano  
<vplhqi$26ur1$5@dont-email.me>

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

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: alt.folklore.computers,comp.os.linux.misc
Subject: Re: The joy of FORTRAN
Date: Tue, 25 Feb 2025 22:56:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <vplhqi$26ur1$5@dont-email.me>
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
	<1smdnSjX3YoxgWf7nZ2dnZfqn_idnZ2d@earthlink.com>
	<llv30aFa6uvU3@mid.individual.net> <vde4b8$268qv$22@dont-email.me>
	<1396870532.749421730.052473.peter_flass-yahoo.com@news.eternal-september.org>
	<wrapper-20241001111737@ram.dialup.fu-berlin.de>
	<vpl5uk$hhk$3@reader1.panix.com> <vpl91g$25q46$1@dont-email.me>
	<1976765442.762208809.808387.peter_flass-yahoo.com@news.eternal-september.org>
	<20250225130315.00004e34@gmail.com> <lhqvP.1323465$if26.592741@fx13.iad>
	<1924764604.762215659.468999.peter_flass-yahoo.com@news.eternal-september.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 25 Feb 2025 23:56:19 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d946ba1e23e7536b5a94a8b1caef1d0d";
	logging-data="2325345"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Cbh3nYj3dZddIdNXpa8j/"
User-Agent: Pan/0.162 (Pokrosvk)
Cancel-Lock: sha1:wDMIxgopp/U9GlR/LqpBH8u0mYg=
Bytes: 2185

On Tue, 25 Feb 2025 15:47:15 -0700, Peter Flass wrote:

> The idea of defining different-sized bytes is a real plus.

What they meant by “bytes” was really just “bitfields”.

With the move to 64-bit addressing, I’ve often felt that it was a missed 
opportunity to reserve the bottom 3 bits for a bit offset within a byte. 
That way, you could have arbitrary bitfield addressing available, without 
any change to the pointer format. Of course it would only be available in 
a select few instructions (e.g. “load bitfield”, “store bitfield”); other 
memory-referencing instructions would either ignore those bottom 3 bits or 
insist they be zero.