search for: 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...

...; 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...

I'm in the process of teaching the Verifier to validate that the size of debug info variable and the described value matches (already caught a couple of bugs, both in my frontend and in LLVM itself). However, I've run into the following: size of passed value (80) does not match size of declared variable (128) call void @llvm.dbg.declare(metadata x86_fp80* %x, metadata !11, metadata