This allows parsing Address Range Tables in 64-bit DWARF format.
Details
Diff Detail
Event Timeline
llvm/test/DebugInfo/X86/dwarfdump-debug-aranges-error-cases.s | ||
---|---|---|
71–72 ↗ | (On Diff #235422) | Not sure if this needs its own test case - since it's the same error/code path for both 32 and 64 bit lengths. (& having only one test for length overrun would enable all the tests to be done in one object file/run, rather than separate RUN lines for each one (some systems, like Windows, have significant per-process overhead so it's nice to keep the total number of separate command invocations down if practical/convenient)) |
llvm/test/DebugInfo/X86/dwarfdump-debug-aranges.s | ||
84 ↗ | (On Diff #235422) | Similar feedback given on other cases - this is probably overcomplicated (given it already has the magic number 7 and 8 - so maybe hardcoding the exact value, rather than this formula, would be simpler - and include a comment about what this achieves) |
llvm/test/DebugInfo/X86/dwarfdump-debug-aranges-error-cases.s | ||
---|---|---|
71–72 ↗ | (On Diff #235422) | This checks that we handle the difference in the length of the initial length field in both formats appropriately. Running additional tests is not a problem anymore, as the tests are moved into a gtest-based suite. As for continuing processing the table after an error, that requires its own patch, where it should be carefully considered, which errors are recoverable. It might be sophisticated, and I am a bit reluctant to do that without a good sample. |