Generate line info for PHI exporters in terminator block

[jiel-nv]

Fixes nvbug5811432.

When stepping through code in cuda-gdb, the debugger would jump to unrelated lines (where variables were last assigned) before reaching the continue statement when the condition is TURE. For example, with this code snippet:

for i in range(5):
    if i == 3:        # line 280
        continue      # line 281
    ...
    x = x + i         # line 295

The debugger would step: 280 → 295 → 281, instead of the expected 280 → 281.

The root cause is during stripping off PHI nodes and creating exporters, a uniformed rhs.loc (the location where the RHS variable was last assigned) is used as the source location. Despite of the existing WITH and WITHOUT assignments cases already handing the place to insert the exporters, the location info are not well handled.

The fix is to conditionally set the loc for PHI exporter assignments:
If the variable is assigned in the current block: Use rhs.loc to preserve the assignment site's location.
If the variable is NOT assigned in the current block (pass-through in continue/break): Use term_loc (the block terminator's location, i.e., the continue/break statement's line number).

Also adds a test test_terminator_line_number into test_debuginfo.

[copy-pr-bot]

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Overview

Greptile Summary

Fixes debugger stepping behavior in cuda-gdb by correctly setting location info for PHI node exporters. Previously, the debugger would jump to unrelated lines where variables were last assigned before reaching continue/break statements. The fix conditionally uses either the assignment site location (when variable is assigned in the block) or the terminator location (for pass-through variables in continue/break blocks). Includes comprehensive test coverage verifying the continue statement line numbers appear correctly in LLVM debug info.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is well-targeted and addresses a specific debugger stepping issue with a logical fix. The implementation correctly handles edge cases (undefined variables, unterminated blocks) and includes comprehensive test coverage that validates the fix works as intended.
• No files require special attention

Important Files Changed

Filename	Overview
numba_cuda/numba/cuda/core/typed_passes.py	Conditionally sets location info for PHI exporter assignments based on whether variable was assigned in current block
numba_cuda/numba/cuda/tests/cudapy/test_debuginfo.py	Adds test to verify continue statement line numbers appear correctly in debug info via LLVM IR inspection

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[jiel-nv]

/ok to test 5e4aef0

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[jiel-nv]

/ok to test 69f94c2

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[jiel-nv]

/ok to test 2b13798

[jiel-nv]

Gentle ping @gmarkall @cpcloud

[cpcloud]

Thanks @jiel-nv!