JuliaGPU/CUDA.jl

Wrong source paths in debug info

Open

#2,460 opened on Aug 6, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Julia (274 forks)batch import
bugcuda kernelsgood first issue

Repository metrics

Stars
 (1,408 stars)
PR merge metrics
 (Avg merge 5d 5h) (16 merged PRs in 30d)

Description

julia> @device_code_ptx raw=true CuArray([1]).+1

	.file	1 "/home/tim/.julia/packages/GPUArrays/8Y80U/src/host/broadcast.jl"
	.file	2 "./int.jl"
	.file	3 "/home/tim/.julia/packages/GPUArrays/8Y80U/src/device/indexing.jl"
	.file	4 "./essentials.jl"
	.file	5 "/home/tim/.julia/packages/LLVM/5DlHM/src/interop/base.jl"
	.file	6 "./broadcast.jl"
	.file	7 "/home/tim/Julia/pkg/CUDA/src/device/array.jl"
	.file	8 "/home/tim/.julia/packages/LLVM/5DlHM/src/interop/pointer.jl"
	.file	9 "./none"

Only package paths seem to be reported correctly. We should try to resolve these to the Julia BINDIR for a better profiling experience.

Contributor guide

Research direction
Investigate the code generating debug info source paths in CUDA.jl. Focus on the compilation pipeline that produces PTX debug info. The goal is to replace relative or package paths with absolute paths under Julia's BINDIR for a better profiling experience.
Tech stack
None
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Julia
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60