Skip to content

Gather node discrepancy for out of index indices #10234

@romain-keramitas-prl

Description

@romain-keramitas-prl

Describe the bug
According to the documentation, indices sent to a Gather node must be in the range [-s, s -1] where s is the first dimension of the data input. An error is indeed raised when the CPUExecutionProvider is used, however that is not the case when the CUDAExecutionProvider is used.

Urgency
Low, we ran into this problem when converting some unit tests that were used with the original model. This may result in silent errors, but in most cases should not be an issue.

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
  • ONNX Runtime installed from (source or binary): binary (wheel)
  • ONNX Runtime version: 1.10
  • Python version: 3.9.9
  • Visual Studio version (if applicable): NA
  • GCC/Compiler version (if compiling from source): NA
  • CUDA/cuDNN version: 11.4
  • GPU model and memory: GeForce RTX 2060, 6GB

To Reproduce

See gist here.

Expected behavior
An error to be raised as well when using the CUDAExecutioonProvider

Screenshots
NA

Additional context
NA

Metadata

Metadata

Assignees

No one assigned

    Labels

    ep:CUDAissues related to the CUDA execution providerstaleissues that have not been addressed in a while; categorized by a bot

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions