Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Tue, 17 Sep 2024 12:52:48 +0300
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <20240917125248.00002a95@yahoo.com>
References: <vaqgtl$3526$1@dont-email.me>
	<p1cvdjpqjg65e6e3rtt4ua6hgm79cdfm2n@4ax.com>
	<2024Sep10.101932@mips.complang.tuwien.ac.at>
	<ygn8qvztf16.fsf@y.z>
	<2024Sep11.123824@mips.complang.tuwien.ac.at>
	<vbsoro$3ol1a$1@dont-email.me>
	<867cbhgozo.fsf@linuxsc.com>
	<20240912142948.00002757@yahoo.com>
	<vbuu5n$9tue$1@dont-email.me>
	<20240915001153.000029bf@yahoo.com>
	<vc6jbk$5v9f$1@paganini.bofh.team>
	<20240915154038.0000016e@yahoo.com>
	<vc70sl$285g2$4@dont-email.me>
	<vc73bl$28v0v$1@dont-email.me>
	<OvEFO.70694$EEm7.38286@fx16.iad>
	<32a15246310ea544570564a6ea100cab@www.novabbs.org>
	<vc7a6h$2afrl$2@dont-email.me>
	<50cd3ba7c0cbb587a55dd67ae46fc9ce@www.novabbs.org>
	<vc8qic$2od19$1@dont-email.me>
	<fCXFO.4617$9Rk4.4393@fx37.iad>
	<vcb730$3ci7o$1@dont-email.me>
	<20240917112114.00003481@yahoo.com>
	<vcbiun$3evls$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 17 Sep 2024 11:52:24 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="230b2ded398db3592516a771801d7f1a";
	logging-data="3586719"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+VNSaPvqNVqY3FbDgbRdl0FDfKzLCua5Y="
Cancel-Lock: sha1:oXJBpToILB4gYT/2fMTtoWyBk+M=
X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
Bytes: 2729

On Tue, 17 Sep 2024 11:42:47 +0200
Terje Mathisen <terje.mathisen@tmsw.no> wrote:

> Michael S wrote:
> > On Tue, 17 Sep 2024 08:20:15 +0200
> > Terje Mathisen <terje.mathisen@tmsw.no> wrote:
> >   
> >> EricP wrote:  
> >>> These double-width bit-field straddle operations show up at
> >>> 32-bits. Various FP64 formats (DEC's middle-endian FP being the
> >>> worst example), Intel page table entries and segment/gate
> >>> descriptors, come to mind.  
> >>
> >> Lots of them in 32-bit code!  
> > 
> > Lot's of what in 32-bit code?
> >   
> 
> Pretty much any 64-bit container with non-regular contents, with the 
> suggest double / fp64 as the classic example?
> 
> Terje
> 

You mean
struct { int a; double b; } where on 32-bit target we expect that b is
not padded? 
And then mantissa of b crosses 64-bit boundary?
But mantissa of b is not accessed as bit field in a typical program.