[llvm-dev] Debug information with clang-cl on Windows (original) (raw)

Jeremy Morse via llvm-dev llvm-dev at lists.llvm.org
Thu Mar 11 03:19:16 PST 2021

Hi,

On the Dexter front, I've found it most useful for small tests in a very tight loop, i.e. modifying a source file and quickly getting some feedback about what kind of debug-info defects are present. Alternately, with opt-bisect-limit to find passes that contribute defects. However, it doesn't work so well with large code bases, we're actively pursing improving that.

There are a few variable-location-coverage improvements in the works -- Stephens patches [0] for variadic variable locations are just landing, although I don't believe they'll be useful for CodeView/PDB targets.

More bug reports about variable locations dropped by clang would be great as we receive very few of them, they're usually not a blocker to developers. Any patterns in what variables go missing would be especially interesting, i.e. "they're usually in lambdas" or "many are loop iterators". That'd help us focus increased testing on those areas.

[0] https://reviews.llvm.org/D91722

-- Thanks, Jeremy

More information about the llvm-dev mailing list