Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Intel: Uninitialized SVM memory is not supported

Open
#252 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
hpc

Research direction

Start with the Julia reproducer using cl.platform!("intel"), CLArray{Int}(undef, 1), and @opencl memset, and compare repeated calls to main(). Trace the Intel execution path for uninitialized SVM memory; done means the reproducer has consistent, correct behavior across repeated runs.

Written by the indexing model from the issue text.

Description

runtime upstream

Intel is one of the few platforms that also supports IL execution, however something seems wrong:

using OpenCL

cl.platform!("intel")

function memset(a, val)
    @inbounds a[1] = val
    return
end

function main()
    a = CLArray{Int}(undef, 1)
    @opencl memset(a, 42)
    Array(a)
end
julia> main()
1-element Vector{Int64}:
 42

julia> main()
1-element Vector{Int64}:
 0

julia> main()
1-element Vector{Int64}:
 0

Not sure yet what the issue is here.

Dominant language
Julia
Stars
313
Forks
50
Avg merge
1d 10h
Merged PRs (30d)
41

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaGPU/OpenCL.jl

All issues in JuliaGPU/OpenCL.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.