This is an archive of the discontinued LLVM Phabricator instance.

[llvm-dwarfdump] Do not print preceding :: for local types
ClosedPublic

Authored by krisb on Dec 1 2021, 10:59 AM.

Diff Detail

Event Timeline

krisb created this revision.Dec 1 2021, 10:59 AM
krisb requested review of this revision.Dec 1 2021, 10:59 AM
Herald added a project: Restricted Project. · View Herald Transcript
dblaikie accepted this revision.Dec 1 2021, 11:37 AM

Looks good, thanks!

This revision is now accepted and ready to land.Dec 1 2021, 11:37 AM

The patch is more about testing generic DebugInfo behaviour, rather than anything specific to llvm-dwarfdump. I wonder if the test would make more sense there? No strong feelings on that though.

krisb added a comment.Dec 2 2021, 3:50 AM

The patch is more about testing generic DebugInfo behaviour, rather than anything specific to llvm-dwarfdump. I wonder if the test would make more sense there? No strong feelings on that though.

I placed the test into the same directory as the original llvm/test/tools/llvm-dwarfdump/X86/prettyprint_types.s, so if to change the directory it should be done for both tests, I think.
If so, I can move both tests in a separate NFC patch, but since there is no strong opinion on where to place these tests, I think this is up to @dblaikie.

The patch is more about testing generic DebugInfo behaviour, rather than anything specific to llvm-dwarfdump. I wonder if the test would make more sense there? No strong feelings on that though.

This comes back to the complication of debug info testing - llvm/test/DebugInfo has ended up as more a place for testing CodeGen/AsmPrinter - debug info generation, though, yeah, that's non-obvious. @probinson did point this out a while back that maybe the LLVM codegen tests should be moved into a different directory so llvm/test/DebugInfo could be used for testing libDebugInfo - and generally it was decided not to do that. I may have second thoughts on that, but generally I'd prefer pure libDebugInfoDWARF testing happen in llvm/test/tools/llvm-dwarfdump (& llvm/test/tools/llvm-symbolizer, etc) for now/these days unless we're going to move the codegen testing out of llvm/test/DebugInfo.

jhenderson accepted this revision.Dec 3 2021, 12:37 AM

The patch is more about testing generic DebugInfo behaviour, rather than anything specific to llvm-dwarfdump. I wonder if the test would make more sense there? No strong feelings on that though.

This comes back to the complication of debug info testing - llvm/test/DebugInfo has ended up as more a place for testing CodeGen/AsmPrinter - debug info generation, though, yeah, that's non-obvious. @probinson did point this out a while back that maybe the LLVM codegen tests should be moved into a different directory so llvm/test/DebugInfo could be used for testing libDebugInfo - and generally it was decided not to do that. I may have second thoughts on that, but generally I'd prefer pure libDebugInfoDWARF testing happen in llvm/test/tools/llvm-dwarfdump (& llvm/test/tools/llvm-symbolizer, etc) for now/these days unless we're going to move the codegen testing out of llvm/test/DebugInfo.

Okay, fair enough. Personal opinion is that there should be a one-to-one mapping between libraries/tools and test directories, which matches @probinson's points, but llvm-dwarfdump is as good as anywhere for this now, I guess (even ignoring the pre-existing test already mentioned).

This revision was landed with ongoing or failed builds.Dec 3 2021, 2:28 AM
This revision was automatically updated to reflect the committed changes.