search for: dw_at_data_bit_offset

That was essentially part of my question. The DWARF standard says: If the value of an object of the given type does not fully occupy the > storage described by a byte size attribute, the base type entry may also > have a DW_AT_bit_size and a DW_AT_data_bit_offset attribute, both of whose > values are integer constant values (see Section 2.19). The bit size > attribute describes the actual size in bits used to represent values of the > given type. The data bit offset attribute is the offset in bits from the > beginning of the containing storage t...

...gt;> That was essentially part of my question. The DWARF standard says: >> >> >> >> If the value of an object of the given type does not fully occupy the >> storage described by a byte size attribute, the base type entry may also >> have a DW_AT_bit_size and a DW_AT_data_bit_offset attribute, both of whose >> values are integer constant values (see Section 2.19). The bit size >> attribute describes the actual size in bits used to represent values of the >> given type. The data bit offset attribute is the offset in bits from the >> beginning of the cont...

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