Skip to content

fix: correct cuTile source locations for generated constants - #1385

Open
Arthur031221 wants to merge 1 commit into
NVIDIA:mainfrom
Arthur031221:fix/type-constant-locations
Open

Arthur031221 wants to merge 1 commit into
NVIDIA:mainfrom
Arthur031221:fix/type-constant-locations

Conversation

@Arthur031221

Copy link
Copy Markdown

Summary

cuTile users compiling with debug info get module-header locations for generated constants and wrapper call sites (#1379). Generated spans were resolved against the module's source base. This addresses the frontend part of #1379. Backend trap attribution remains unverified.

Changes

Resolve captured spans with their owning module and use the containing function definition for generated spans. The regression uses @elibol's assertion kernel from #1379.

Testing

Added line/full and cross-file regressions. From cutile-rs, cargo +1.98.0 test -p cutile --locked --test debug_info passes.

  • just -f cuda-oxide/Justfile check passes (the local mirror of CI: fmt, clippy, tests, guards, docs)
  • cargo oxide run <example> passes, or cuda-oxide/scripts/smoketest.sh -o '^<example>$'
  • New example added (if applicable)

Checklist

  • All commits signed off (git commit -s)
  • SPDX headers on new source files

Questions about the review? Ping us in #contributors on Discord.

Co-authored-by: Melih Elibol 1884921+elibol@users.noreply.github.com

Use captured module spans for source locations and the current function
definition for generated types, arrays and wrapper calls. Add regressions
using the assertion kernel from NVIDIA#1379 and a helper in another file.

Co-authored-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Arthur031221 <levi74108520963@gmail.com>
@Arthur031221
Arthur031221 requested a review from elibol as a code owner October 3, 2026 20:44
@copy-pr-bot

copy-pr-bot Bot commented Oct 3, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant