Displaying 1 result from an estimated 1 matches for "llvmfieldno".
2009 Feb 19
2
[LLVMdev] please review this fix for PR3510
...The patched code tracks the HighWaterMarkInBits; it points to the next
bit to allocate. If the starting offset of the next initializing
value doesn't match, either byte-alignment or padding is indicated.
FieldNo counts the fields (initializers or padding) created in
ResultElts[], and LLVMFieldNo walks through the LLVM structure type
fields. Note that ResultElts[] is now created to hold 2X the number
of LLVM fields in order to accommodate padding fields; it is shrunk-to-
fit after the initializer is complete.
I've seen hints in the code that C++ can generate overlapping field
d...