summaryrefslogtreecommitdiffstats
path: root/llvm/test/tools/llvm-dwp/Inputs
Commit message (Collapse)AuthorAgeFilesLines
* [llvm-dwp] Abort when dwo_id is unsetJordan Rupprecht2019-02-121-0/+0
| | | | | | | | | | | | | | | | | | | Summary: An empty dwo_id indicates a degenerate .dwo file that should not have been generated in the first place. Instead of discovering this error later when merging with another degenerate .dwo file, print an error immediately when noticing an unset dwo_id, including the filename of the offending file. Test case created by compiling a trivial file w/ `-fno-split-dwarf-inlining -gmlt -gsplit-dwarf -c` prior to r353771 Reviewers: dblaikie Reviewed By: dblaikie Subscribers: jdoerfert, aprantl, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D58085 llvm-svn: 353846
* [llvm-dwp] Implement -e optionAlexander Shaposhnikov2017-09-027-0/+0
| | | | | | | | | | | | | | | The binutils utility dwp has an option "-e" https://gcc.gnu.org/wiki/DebugFissionDWP to specify an executable/library to get the list of *.dwo files from it. This option is particularly useful when someone runs the tool manually outside of a build system. This diff adds an implementation of "-e" to llvm-dwp. Test plan: make check-all Differential revision: https://reviews.llvm.org/D37371 llvm-svn: 312409
* llvm-dwp: More error handling around invalid compressed sectionsDavid Blaikie2016-05-232-0/+0
| | | | llvm-svn: 270466
* llvm-dwp: Add error handling for multiple type sections in a dwp file.David Blaikie2016-05-171-0/+0
| | | | llvm-svn: 269851
* llvm-dwp: Provide error handling for invalid string field formsDavid Blaikie2016-05-171-0/+0
| | | | | | | | | | This diagnostic could be improved by adding the name of the input file containing the invalid data and/or some information about how to identify the specific offending attribute/tag in the input. But that's not an immediate priority as these corner cases of invalid input shouldn't come up too often. llvm-svn: 269727
* llvm-dwp: Add error handling for invalid (non-CU) top level tag in ↵David Blaikie2016-05-161-0/+0
| | | | | | | | | | debug_info.dwo The diagnostic could be improved a bit to include information about which input file had the mistake (& which unit (counted, since the name of the unit won't be accessible) within the input). llvm-svn: 269723
* llvm-dwp: Use llvm::Error to improve diagnostic quality/error handling in ↵David Blaikie2016-05-125-0/+0
| | | | | | llvm-dwp llvm-svn: 269339
* llvm-dwp: Handle dwo files produced by GCCDavid Blaikie2016-04-051-0/+0
| | | | | | | To start with, handle DW_FORM_string names. Follow up commit will handle the interesting quirk with type units I was originally aiming for here. llvm-svn: 265452
* llvm-dwp: Include the dwo name (if available) when diagnosing duplicate CU ↵David Blaikie2016-03-263-0/+0
| | | | | | | | | | | | IDs from dwp input files If you're building dwps from other dwps, it can be hard to track down a duplicate CU ID if it comes from two compilations of the same file in different modes, etc. By including the .dwo path (which is hopefully more unique than the file path) it can help track down where the duplicates came from. llvm-svn: 264520
* llvm-dwp: provide diagnostics for duplicate DWO IDsDavid Blaikie2016-02-263-0/+0
| | | | | | | | | | | | | | These diagnostics aren't perfect - in the case of merging several dwos into dwps and those dwps into more dwps - just getting the message about the original source file name might not be much help (since it's the same in both dwos, by definition - but doesn't tell you which chain of dwps to backtrack) It might be worth adding the DW_AT_dwo_id to the split debug info to improve the diagnostic experience - might help track down the duplicates better. llvm-svn: 261988
* llvm-dwp: Support empty .dwo filesDavid Blaikie2016-02-261-0/+0
| | | | | | | | | Though a bit odd, this is handy for a few reasons - for example, in a build system that wants consistent input/output of build steps, but where split-dwarf might be overriden/disabled by the user on a per-file basis. llvm-svn: 261987
* llvm-dwp: Support compressed inputDavid Blaikie2016-02-191-0/+0
| | | | llvm-svn: 261296
* [llvm-dwp] Merge cu_index from DWPsDavid Blaikie2016-02-062-0/+0
| | | | | | This is almost feature complete - just missing tu_index merging now. llvm-svn: 259971
* [llvm-dwp] Deduplicate type unitsDavid Blaikie2015-12-142-0/+0
| | | | | | | | It's O(N^2) because it does a simple walk through the existing types to find duplicates, but that will be fixed in a follow-up commit to use a mapping data structure of some kind. llvm-svn: 255482
* [llvm-dwp] Remove some unused test codeDavid Blaikie2015-12-142-5/+0
| | | | llvm-svn: 255481
* [llvm-dwp] Restructure inputs for test case so they're all grouped togetherDavid Blaikie2015-12-074-0/+0
| | | | llvm-svn: 254922
* [llvm-dwp] Add coverage for both the presence and absence of type units, and ↵David Blaikie2015-12-052-0/+0
| | | | | | fix/remove the emission of a broken tu_index when no type units are present llvm-svn: 254833
* [llvm-dwp] Rename the sufficiently-modified test to reflect it's non-simplicityDavid Blaikie2015-12-054-0/+0
| | | | llvm-svn: 254829
* [llvm-dwp] Support debug_tu_indexDavid Blaikie2015-12-052-0/+0
| | | | llvm-svn: 254827
* [llvm-dwp] Initial partial prototypeDavid Blaikie2015-12-014-0/+5
This just concatenates the common DWP sections without doing any of the fancy DWP things like: 1) update str_offsets 2) deduplicating strings 3) merging/creating cu/tu_index Patches for these will follow shortly. (also not sure about target triple/object file type for this tool - do I really need a whole triple just to write an object file that contains purely static/hardcoded bytes in each section? & I guess I should just pick it based on the first input, maybe, rather than hardcoding for now - but we only produce .dwo on ELF platforms with objcopy for now anyway) llvm-svn: 254355
OpenPOWER on IntegriCloud