mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 12:12:47 +01:00
980f06a21f
This isn't the most robust error handling API, but does allow clients to opt-in to getting Errors they can handle. I suspect the long-term solution would be to move away from the lazy unit parsing and have an explicit step that parses the unit and then allows access to the other APIs that require a parsed unit. llvm-dwarfdump could be expanded to use this (or newer/better API) to demonstrate the benefit of it - but for now lld will use this in a follow-up cl which ensures lld can exit non-zero on errors like this (& provide more descriptive diagnostics including which object file the error came from). (error access to later errors when parsing nested DIEs would be good too - but, again, exposing that without it being a hassle for every consumer may be tricky) llvm-svn: 368377 |
||
---|---|---|
.. | ||
DWARFAbbreviationDeclaration.h | ||
DWARFAcceleratorTable.h | ||
DWARFAddressRange.h | ||
DWARFAttribute.h | ||
DWARFCompileUnit.h | ||
DWARFContext.h | ||
DWARFDataExtractor.h | ||
DWARFDebugAbbrev.h | ||
DWARFDebugAddr.h | ||
DWARFDebugAranges.h | ||
DWARFDebugArangeSet.h | ||
DWARFDebugFrame.h | ||
DWARFDebugInfoEntry.h | ||
DWARFDebugLine.h | ||
DWARFDebugLoc.h | ||
DWARFDebugMacro.h | ||
DWARFDebugPubTable.h | ||
DWARFDebugRangeList.h | ||
DWARFDebugRnglists.h | ||
DWARFDie.h | ||
DWARFExpression.h | ||
DWARFFormValue.h | ||
DWARFGdbIndex.h | ||
DWARFListTable.h | ||
DWARFObject.h | ||
DWARFRelocMap.h | ||
DWARFSection.h | ||
DWARFTypeUnit.h | ||
DWARFUnit.h | ||
DWARFUnitIndex.h | ||
DWARFVerifier.h |