DW_FORM_sec_offset was introduced in DWARFv4, so, for 64-bit DWARFv3, DW_FORM_data8 should be used instead.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/MC/ELF/gen-dwarf64.s | ||
---|---|---|
17 | At least a "REL-NOT: }" to check that you haven't accidentally jumped into another section's relocations might be useful? But really that'd have to go between every one of these check lines. Perhaps llvm-readobj has flags that specify which sections to dump - and if you only dump the relocations for the sections you're interested in, then you could use an --implicit-check-not: Section, for instance - to ensure you didn't jump over any section headers. |
llvm/test/MC/ELF/gen-dwarf64.s | ||
---|---|---|
17 | You probably meant "REL-NOT: {", but that still would not have helped with missed ,REL3. |
llvm/test/MC/ELF/gen-dwarf64.s | ||
---|---|---|
17 | You could add a REL: } check to mark the end of the .rela.debug_info, which would allow for the next bit to be REL-NEXT, but that also wouldn't solve the problem. This sounds like one of those FileCheck gotchas, and I can't see much we can do in the test to avoid it in this case. You could maybe use something like --implicit-check-not=.debug to show that there are no relocations targeting debug sections in the output except for those explicitly checked, maybe? |
--check-prefixes=REL,REL3