File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -424,16 +424,16 @@ Using Coverage Tracking to remove false positives
424
424
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
425
425
426
426
As described :ref: `above<WhenToDropLocation> `, there are valid reasons for
427
- instructions to have missing source locations. Therefore, when detecting dropped
428
- or not-generated source locations, it may be preferred to avoid detecting cases
427
+ instructions to not have source locations. Therefore, when detecting dropped or
428
+ not-generated source locations, it may be preferable to avoid detecting cases
429
429
where the missing source location is intentional. For this, you can use the
430
430
"coverage tracking" feature in LLVM to prevent these from appearing in the
431
431
``debugify `` output. This is enabled in a build of LLVM by setting the CMake
432
432
flag ``-DLLVM_ENABLE_DEBUGLOC_COVERAGE_TRACKING=COVERAGE ``. When this has been
433
433
set, LLVM will enable runtime tracking of
434
434
:ref: `DebugLoc annotations<_NewInstLocations> `, allowing ``debugify `` to ignore
435
- instructions that have an explicit reason given for not having a source
436
- location.
435
+ instructions that have an explicitly recorded reason given for not having a
436
+ source location.
437
437
438
438
For triaging source location bugs detected with ``debugify ``, you may find it
439
439
helpful to instead set the CMake flag
You can’t perform that action at this time.
0 commit comments