search for: getlongdoubesize

...it's TargetInfo Just to throw my opinion out there: 1) Use the DW_AT_bit_size/DW_AT_byte_size 2) Add a new `storage_size` attribute to DIBaseType that is generally equal to size, except in cases like this, where we should have `storage_size = 128, size = 80` 3) Have clang set those based on `getLongDoubeSize` (for storage size) and `getLongDoubleFormat` as Reid suggested. This did seem very hacky too me at first as well, but thinking about it again, the format does encode how many semantic bits there are (because it is needed for correctly constant folding etc.), which is really what we're asking f...

...> existing field & have to worry about breaking back compat?) - the >> new/differently named field should describe the new thing we want to add, >> the actual functional size (not sure what to name it, though)? >> >> >> >> 3) Have clang set those based on `getLongDoubeSize` (for storage size) >> and `getLongDoubleFormat` as Reid suggested. This did seem very hacky too >> me at first as well, but thinking about it again, the format does encode >> how many semantic bits there are (because it is needed for correctly >> constant folding etc.), whi...

On Mon, Nov 2, 2015 at 8:38 AM, Adrian Prantl via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Looking at the code in clang CGDebugInfo just passes through the width of > the type as it is described by the TypeInfo, which in turn is defined by > the Target. At the moment I do not understand why an x86_fp80 is reported > to be 128 bits wide. (Since it’s a type natively