JuliaArrays / JuliaArrays/ArrayInterface.jl
Bug in `device` for reshaped views
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 140
- Forks
- 44
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 5
Description
Reported by @chriselrod in https://github.com/JuliaArrays/ArrayInterface.jl/pull/156#issuecomment-851293134:
julia> using ArrayInterface julia> u_base = randn(10, 10); u_view = view(u_base, 2:3, :); u_reshaped_view = reshape(u_view, 1, length(u_view)); julia> ArrayInterface.device(u_reshaped_view) ArrayInterface.CPUPointer()This
u_reshaped_viewis not strided, so it should not be aCPUPointer(), but aCPUIndex()(which currently is not supported by LoopVectorization).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Julia example involving ArrayInterface.device on a reshaped view, then inspect how reshaped and strided views are classified. Done means the non-strided reshaped view is identified as CPUIndex rather than CPUPointer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100