News for hackers. Stuff that matters.
Re:C++ proposal: There are 8 bits in a byte by wvenable on Thursday October 17, 2024 @07:27PM (#41874838)
"Word" is an outdated concept we should try to get rid of.
Re:C++ proposal: There are 8 bits in a byte by anigbrowl on Thursday October 17, 2024 @07:33PM (#41874892)
You're right. To be consistent with bytes we should call it a snack.
Re:C++ proposal: There are 8 bits in a byte by SCUSKU on Thursday October 17, 2024 @07:42PM (#41874949)
Henceforth, it follows that a doublesnack is called a lunch. And a quadruplesnack a fourthmeal.
Re:C++ proposal: There are 8 bits in a byte by tetron on Thursday October 17, 2024 @08:18PM (#41875163)
There's only one right answer:

Nybble - 4 bits

Byte - 8 bits

Snyack - 16 bits

Lyunch - 32 bits

Dynner - 64 bits

Re:C++ proposal: There are 8 bits in a byte by kstrauser on Thursday October 17, 2024 @11:04PM (#41876019)
In the spirit of redefining the kilobyte, we should define byte as having a nice, metric 10 bits. An 8 bit thing is obviously a bibyte. Then power of 2 multiples of them can include kibibibytes, mebibibytes, gibibibytes, and so on for clarity.
Re:C++ proposal: There are 8 bits in a byte by jaysonvantuyl on Thursday October 17, 2024 @11:20PM (#41876085)
ಠ_ಠ
Re:C++ proposal: There are 8 bits in a byte by cozzyd on Thursday October 17, 2024 @09:51PM (#41875680)
And what about elevensies?

(Ok,. I guess there's a difference between bits and hob-bits)

Re:C++ proposal: There are 8 bits in a byte by xigoi on Friday October 18, 2024 @12:08PM (#41880712)
This is incompatible with cultures where lunch is bigger than dinner.
Re:C++ proposal: There are 8 bits in a byte by iwaztomack on Thursday October 17, 2024 @07:47PM (#41874984)
or an f-word
Re:C++ proposal: There are 8 bits in a byte by pclmulqdq on Thursday October 17, 2024 @07:32PM (#41874888)
It's very useful on hardware that is not an x86 CPU.
Re:C++ proposal: There are 8 bits in a byte by wvenable on Thursday October 17, 2024 @07:39PM (#41874937)
As an abstraction on the size of a CPU register, it really turned out to be more confusing than useful.
Re:C++ proposal: There are 8 bits in a byte by pclmulqdq on Thursday October 17, 2024 @08:02PM (#41875078)
On RISC machines, it can be very useful to have the concept of "words," because that indicates things about how the computer loads and stores data, as well as the native instruction size. In DSPs and custom hardware, it can indicate the only available datatype.

The land of x86 goes to great pains to eliminate the concept of a word at a silicon cost.

Re:C++ proposal: There are 8 bits in a byte by o11c on Thursday October 17, 2024 @07:51PM (#41875003)
Fortunately we have `register_t` these days.
Re:C++ proposal: There are 8 bits in a byte by bobmcnamara on Thursday October 17, 2024 @07:49PM (#41874993)
Is it 32 or 64 bits on ARM64? Why not both?
Re:C++ proposal: There are 8 bits in a byte by billti on Friday October 18, 2024 @01:42AM (#41876643)
ARM64 has a 32-bit word, even though the native pointer size and general register size is 64 bits. To access just the lower 32 bits of a register Xn you refer to it as Wn.
Re:C++ proposal: There are 8 bits in a byte by iwaztomack on Thursday October 17, 2024 @07:47PM (#41874988)
such as...?
Re:C++ proposal: There are 8 bits in a byte by BlueTemplar on Thursday October 17, 2024 @07:38PM (#41874933)
How exactly ? How else do you suggest CPUs do addressing ?

Or are you suggesting to increase the size of a byte until it's the same size as a word, and merge both concepts ?

Re:C++ proposal: There are 8 bits in a byte by wvenable on Thursday October 17, 2024 @07:43PM (#41874963)
I'm saying the term "Word" abstracting the number of bytes a CPU can process in a single operation is an outdated concept. We don't really talk about word-sized values anymore. Instead we mostly explicit on the size of value in bits. Even the idea of a CPU having just one relevant word size is a bit outdated.
Re:C++ proposal: There are 8 bits in a byte by kevin_thibedeau on Thursday October 17, 2024 @10:25PM (#41875850)
Appeasing that attitude is what prevented Microsoft from migrating to LP64. Would have been an easier task if their 32-bit LONG type never existed, they stuck with DWORD, and told the RISC platforms to live with it.