Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
One comment inline.
llvm/tools/llvm-dwarfdump/Statistics.cpp | ||
---|---|---|
721 | This comment is mostly repeats what's already in the name of the variable. It might more interesting to explain why these are being reset for each CU. |
Generally good for me - but could you try to see if the test could be simplified any further (maybe "main" can be in test1 or test2 (replacing f1 or f2) and could call the other function in the other file) - and see if the auxiliary/input files could be represented as assembly instead of checked in object files?
I am not sure how to keep this as assembly code, since we'd need to create object files of it, and then to link it together...
the dwo files should be able to be assembly without any particular restrictions/complications in authoring them, right? (taking the assembly of a split DWARF compilation and pulling out the .dwo parts should be adequate, I think)
The executable - it could probably actually be an object file that happens to have two skeleton units in it (like we generate under LTO, for instance - though without any of the LTO-specific cross-CU references) so that could be written in assembly relatively easily (to hand-craft it you could probably take the assembly of the two skeletons and copy/paste them into one file for instance)
llvm/test/tools/llvm-dwarfdump/X86/inlined_variables_with_zero_cov.test | ||
---|---|---|
31 | Output files should go in %t or a subdirectory of %t, so things like: RUN: rm -r %t RUN: mkdir %t RUN: ... -o %t/test1.dwo ... |
Output files should go in %t or a subdirectory of %t, so things like: