Re: 64 bit or 32 bit

From: Måns Rullgård (mru_at_kth.se)
Date: 04/07/04 

Date: Wed, 07 Apr 2004 17:10:10 +0200

Grant Edwards <grante@visi.com> writes:

> On 2004-04-07, Måns Rullgård <mru@kth.se> wrote:
>
>> So when processors become 256-bit, what will we get?
>>
>> char = 8 bits
>> short short = 16 bits
>> short = 32 bits
>> long short = 64 bits
>> int = 128 bits
>> long = 256 bits
>
> It really get's confusing when we need even more types and
>
> "long short" and "short long" aren't the same thing.
>
> OTOH, if you want a certain number of bits, you should probably
> just ask for them directly using <stdint.h> and int32_t or
> uint16_t or int47_t or whatever.

True, but the compiler has to have types to back those typedefs. 

-- 
Måns Rullgård
mru@kth.se

Relevant Pages

  • Re: Totally stuck
    ... OTOH I was too lazy to try to understand ... the following should serve your needs and is considerably ... Very confusing, ...
    (comp.lang.perl.misc)
  • Re: Any uC manufacturers have free c compilers?
    ... Grant Edwards writes: ... Are the versions shipped really as ancient as those listed on ... confusing sections myself, and they agreed to use my changes. ... Hopefully it's more obvious what we do, without miscommunicating ...
    (comp.arch.embedded)
  • Re: Bit width?
    ... Grant Edwards wrote in ... > The confusing thing is that a monetary bit is a half of a ... Which would be par for the course for the antiquated measurement system ...
    (comp.arch.embedded)