Skip to content

Correctness issue when indexing "big" oneArrays #509

Description

@cncastillo

I was debugging some Buildkite CI errors in KomaMRI and narrowed the issue down to indexing into a matrix that's “too big.” This is a MWE:

using oneAPI
x = randn(Float32, 513, 3)
x_one = convert(oneArray, x)
julia> y = x[:, 1:2]
513×2 Matrix{Float32}:
 -0.785065    0.605889
 -0.138269   -0.886778
 -0.418909   -0.302653
 -0.0957128  -0.974546
  ⋮          
 -0.486535   -0.594906
  1.42615    -1.00182
  0.0519026  -0.0332484

julia> y_one = x_one[:, 1:2]
513×2 oneArray{Float32, 2, oneAPI.oneL0.DeviceBuffer}:
 -0.785065    0.0
 -0.138269    0.0
 -0.418909    0.0
 -0.0957128   0.0
  ⋮          
 -0.486535    0.0
  1.42615    -1.00182
  0.0519026  -0.0332484

Which is very interesting, as it does not happen when using views:

julia> y = @view x[:, 1:2]
513×2 view(::Matrix{Float32}, :, 1:2) with eltype Float32:
 -0.785065    0.605889
 -0.138269   -0.886778
 -0.418909   -0.302653
 -0.0957128  -0.974546
  ⋮          
 -0.486535   -0.594906
  1.42615    -1.00182
  0.0519026  -0.0332484

julia> y_one = @view x_one[:, 1:2]
513×2 oneArray{Float32, 2, oneAPI.oneL0.DeviceBuffer}:
 -0.785065    0.605889
 -0.138269   -0.886778
 -0.418909   -0.302653
 -0.0957128  -0.974546
  ⋮          
 -0.486535   -0.594906
  1.42615    -1.00182
  0.0519026  -0.0332484

I am using Julia 1.11.6 and oneAPI 2.0.3. Not really sure what could be the cause, but when I use x = randn(Float32, 512, 3) it starts working again, so it seems to be related to the size of the array.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions