search for: getstoragetypesizeinbit

...think rather than worrying about how these functions are being used > *now* you should define them in a way that's clear and fix the > incorrect uses. To me that means: > > getTypeSizeInBits - actual size > getABITypeSizeInBits - ABI size when used in a larger structure > getStorageTypeSizeInBits - size of load / store I agree and will try to do something later this week. Ciao, Duncan. PS: getStorageTypeSizeInBits -> getTypeStorageSizeInBits

...meaning, and seems useful. I think rather than worrying about how these functions are being used *now* you should define them in a way that's clear and fix the incorrect uses. To me that means: getTypeSizeInBits - actual size getABITypeSizeInBits - ABI size when used in a larger structure getStorageTypeSizeInBits - size of load / store > >>> Clearly getABITypeSize corresponds to (5) [except that it's in >>> bytes]. This >>> corresponds to gcc's TYPE_SIZE. >> >> Right. >> >>> >>> Currently getABITypeSizeInBits returns 36 for i36, an...

Hi Evan, thanks for replying. > > Now that I'm working on codegen support for arbitrary precision > > integers (think i36 or i129), I've hit the problem of what > > getTypeSize and friends should return for such integers (the > > current implementations seem to me to be wrong). However it's > > not clear to me how getTypeSize and friends are defined.