search for: abitypesize

...'s part of a larger object (i.e. 40?). > > Another example is 80-bit floating point types. Here (1), (2) > and (3) are presumably 80 bits. On my machine (5) is 96 bits. > I'm not sure what (4) is, presumably 80 or 96. > > Which (if any) of these should getTypeSize, getABITypeSize, > getTypeSizeInBits > and getABITypeSizeInBits correspond to? TypeSize == "real size", ABITypeSize == "abi size". You will need another pair for the storage size? > > It seems clear that getTypeSizeInBits corresponds to (1) and (2), as > shown by it returni...

...sn't seem worth the trouble. > Should (4) be the same as (5) since alloca / malloc are allocating an > array of the specific type? Yes, I think so. Currently alloca allocates a multiple of getTypeSize (see visitAlloca in SelectionDAGISel). This seems to be a bug - it needs to use getABITypeSize. This also means that all the (many) places that use getTypeSize as the amount of memory allocated by an alloca need to be changed... > > In general (1) and (2) will be the same. (4) needs to be at least > > as big as (3). (5) needs to be at least as big as (4). > > Do you re...

...ds to be at least as big as (3). (5) needs to be at least as big as (4). Another example is 80-bit floating point types. Here (1), (2) and (3) are presumably 80 bits. On my machine (5) is 96 bits. I'm not sure what (4) is, presumably 80 or 96. Which (if any) of these should getTypeSize, getABITypeSize, getTypeSizeInBits and getABITypeSizeInBits correspond to? It seems clear that getTypeSizeInBits corresponds to (1) and (2), as shown by it returning 36 for i36. This is like gcc's TYPE_PRECISION, and is a useful concept - but I think the name should be changed, since right now it implicitly...

...r. > >> Should (4) be the same as (5) since alloca / malloc are allocating an >> array of the specific type? > > Yes, I think so. Currently alloca allocates a multiple of getTypeSize > (see visitAlloca in SelectionDAGISel). This seems to be a bug - it > needs to use getABITypeSize. This also means that all the (many) > places > that use getTypeSize as the amount of memory allocated by an alloca > need > to be changed... Hrm. It does seem like it could be a bug. I am not too familiar with the code so someone please verify this. Chris? > >>> In...