Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: comp.arch Subject: Re: Keeping other stuff with addresses Date: Tue, 03 Dec 2024 13:46:01 -0500 Organization: A noiseless patient Spider Lines: 15 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Tue, 03 Dec 2024 19:46:02 +0100 (CET) Injection-Info: dont-email.me; posting-host="5e8f21e9800beeb82e87504d9059946a"; logging-data="280026"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+18dmO1VJLlwgftr1mNz2N5IZ6OiPMYDE=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:AeQ44ZLy0ROPdwGAG+qygrMxHIM= sha1:b2ALRfG5t7VJ8QzwejL+VjDbozk= Bytes: 1780 >>> another way to steal bits is over alignment. >>Yup. I keep lamenting that Alpha didn't go for bit-addressed memory, >>which would have given us 3 extra free bits from alignment (as well as >>allowing pointers to bits and bitfields). > I thought STRETCH persuaded people that bit addressable memory was a bad idea. Yes, but that was a misunderstanding. I'm not suggesting that load/store instructions can access things at any bit position and any bit size. Any load or store with a pointer whose last 3 bits is not 0 would presumably signal en error. Just like the 21064 Alpha where they had byte-addressed memory but the load/store instructions could only handle aligned words. Stefan