search for: highwatermarkinbits

...LLVM fields and the initializer in lock-step. Alas, that fails when the initializer requires alignment padding; such padding is not recorded in the LLVM structure type. This implies that the initialized ResultElts[] may have many more fields than the LLVM type. 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 typ...