aboutsummaryrefslogtreecommitdiff
path: root/clang/unittests/Format/ConfigParseTest.cpp
diff options
context:
space:
mode:
authorKevin Frei <kevinfrei@users.noreply.github.com>2024-02-12 16:57:02 -0800
committerGitHub <noreply@github.com>2024-02-12 16:57:02 -0800
commit3bdc4c702dfdd1f2fb513943f034d49bb79ded29 (patch)
tree15424e1d3e753c975dbef468a4b03c50ffd5beab /clang/unittests/Format/ConfigParseTest.cpp
parenta38152e2156a467520dae29fa3760802c308d54c (diff)
downloadllvm-3bdc4c702dfdd1f2fb513943f034d49bb79ded29.zip
llvm-3bdc4c702dfdd1f2fb513943f034d49bb79ded29.tar.gz
llvm-3bdc4c702dfdd1f2fb513943f034d49bb79ded29.tar.bz2
Gsymutil aggregation similar to DwarfDump --verify (#81154)
GsymUtil, like DwarfDump --verify, spews a *lot* of data necessary to understand/diagnose issues with DWARF data. The trouble is that the kind of information necessary to make the messages useful also makes them nearly impossible to easily categorize. I put together a similar output categorizer (https://github.com/llvm/llvm-project/pull/79648) that will emit a summary of issues identified at the bottom of the (very verbose) output, enabling easier tracking of issues as they arise or are addressed. There's a single output change, where a message "warning: Unable to retrieve DWO .debug_info section for some object files. (Remove the --quiet flag for full output)" was being dumped the first time it was encountered (in what looks like an attempt to make something easily grep-able), but rather than keep the output in the same order, that message is now a 'category' so gets emitted at the end of the output. The test 'tools/llvm-gsymutil/X86/elf-dwo.yaml' was changed to reflect this difference. --------- Co-authored-by: Kevin Frei <freik@meta.com>
Diffstat (limited to 'clang/unittests/Format/ConfigParseTest.cpp')
0 files changed, 0 insertions, 0 deletions