Re:The future of 32-bit support in the kernel
by cardiffspaceman on Monday September 01, 2025 @06:30PM
(#45097180)
On the DEC-10 the word size is 36 bits. There was (an option to include) a special set of instructions to enable any given byte size with bytes packed. Five 7-bit bytes per word, for example, with a wasted bit in each word.
I wouldn’t be surprised if other machines had something like this in hardware.
Re:The future of 32-bit support in the kernel
by Affric on Monday September 01, 2025 @11:02PM
(#45098727)
Could you use the extra bit for parity?
Re:The future of 32-bit support in the kernel
by cardiffspaceman on Tuesday September 02, 2025 @04:29PM
(#45108581)
I don’t remember if there are instructions for putting any value of parity as such into the spare bit.
Re:The future of 32-bit support in the kernel
by int_19h on Monday September 01, 2025 @09:43PM
(#45098268)
> For the representation of text of an alphabetic language, you need to hit 6 bits if your script doesn't have case
Only if you assume a 1:1 mapping. But e.g. the original Baudot code was 5-bit, with codes reserved to switch between letters and "everything else". When ASCII was designed, some people wanted to keep the same arrangement.
Re:The future of 32-bit support in the kernel
by goku12 on Monday September 01, 2025 @11:19PM
(#45098810)
I wasn't asking about word sizes in particular, and had ASCII in mind. Nevertheless, your answer is in the right direction.
Re:The future of 32-bit support in the kernel
by dboreham on Tuesday September 02, 2025 @12:00AM
(#45099014)
Quick note that parity was never used in "characters stored". It was only ever used in transmission, and checked/removed by hardware[1].
[1] Yes, I remember you could bit-bang a UART in software, but still the parity bit didn't escape the serial decoding routine.
For the representation of text of an alphabetic language, you need to hit 6 bits if your script doesn't have case and 7 bits if it does have case. ASCII ended up encoding English into 7 bits and EBCDIC chose 8 bits (as it's based on a binary-coded decimal scheme which packs a decimal digit into 4 bits). Early machines did choose to use the unused high bit of an ASCII character stored in 8 bits as a parity bit, but most machines have instead opted to extend the character repertoire in a variety of incompatible ways, which eventually led to Unicode.