Skip to content

Commit 07bc7eb

Browse files
committed
Update doc wording slightly
1 parent 3a91e60 commit 07bc7eb

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

llvm/docs/HowToUpdateDebugInfo.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -424,16 +424,16 @@ Using Coverage Tracking to remove false positives
424424
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
425425

426426
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
429429
where the missing source location is intentional. For this, you can use the
430430
"coverage tracking" feature in LLVM to prevent these from appearing in the
431431
``debugify`` output. This is enabled in a build of LLVM by setting the CMake
432432
flag ``-DLLVM_ENABLE_DEBUGLOC_COVERAGE_TRACKING=COVERAGE``. When this has been
433433
set, LLVM will enable runtime tracking of
434434
: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.
437437

438438
For triaging source location bugs detected with ``debugify``, you may find it
439439
helpful to instead set the CMake flag

0 commit comments

Comments
 (0)