diff options
| author | Djordje Todorovic <djordje.todorovic@syrmia.com> | 2021-05-21 01:57:23 -0700 |
|---|---|---|
| committer | Djordje Todorovic <djtodoro@cisco.com> | 2021-05-21 02:04:29 -0700 |
| commit | b9076d119a5b2d380d8868ee5e4dc4fdc5ba04a6 (patch) | |
| tree | 1ad90a7a92d24a5b92abd998bc3dba35f4e7c341 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
| parent | fb8b2b86d3d1ba6e26a5d9296e2b235eb36d10b8 (diff) | |
Recommit: "[Debugify][Original DI] Test dbg var loc preservation""
[Debugify][Original DI] Test dbg var loc preservation
This is an improvement of [0]. This adds checking of
original llvm.dbg.values()/declares() instructions in
optimizations.
We have picked a real issue that has been found with
this (actually, picked one variable location missing
from [1] and resolved the issue), and the result is
the fix for that -- D100844.
Before applying the D100844, using the options from [0]
(but with this patch applied) on the compilation of GDB 7.11,
the final HTML report for the debug-info issues can be found
at [1] (please scroll down, and look for
"Summary of Variable Location Bugs"). After applying
the D100844, the numbers has improved a bit -- please take
a look into [2].
[0] https://llvm.org/docs/HowToUpdateDebugInfo.html#\
test-original-debug-info-preservation-in-optimizations
[1] https://djolertrk.github.io/di-check-before-adce-fix/
[2] https://djolertrk.github.io/di-check-after-adce-fix/
Differential Revision: https://reviews.llvm.org/D100845
The Unit test was failing because the pass from the test that
modifies the IR, in its runOnFunction() didn't return 'true',
so the expensive-check configuration triggered an assertion.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions
