On Thu, 13 Sep 2001 06:27:27 +0300 [ooh I'm far behind on these lists], Jarkko Hietaniemi wrote: >I always see this claim ("why would you use 64 bits unless you really >need them big, they must be such a waste") being bandied around, without >much hard numbers to support the claims. >Unless you are thinking of huge and/or multidimensional arrays >of tightly packed integers, I don't think you should care. We're talking bytecode. That will indeed be a case of "huge arrays of tightly packed integers". -- Bart.
- Re: Using int32_t instead of IV for code Philip Kendall
- Re: Using int32_t instead of IV for code Andy Dougherty
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Buddha Buck
- Re: Using int32_t instead of IV for code Paul Johnson
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Philip Kendall
- RE: Using int32_t instead of IV for code Hong Zhang
- Re: Using int32_t instead of IV for code Jarkko Hietaniemi
- Re: Using int32_t instead of IV for code Simon Cozens
- Re: Using int32_t instead of IV for code Bart Lateur
- Re: Using int32_t instead of IV for code Michael Maraist
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Michael Maraist
- Re: Using int32_t instead of IV for code Bart Lateur
- Re: Using int32_t instead of IV for code Michael Maraist
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Nathan Torkington