Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes to checking validity of a range. #876

Merged
merged 1 commit into from
Jan 19, 2023
Merged

Fixes to checking validity of a range. #876

merged 1 commit into from
Jan 19, 2023

Conversation

diptorupd
Copy link
Collaborator

  • Have you provided a meaningful PR description?
    • Removes superfluous copy inside JitKernel.getitem
    • Improves the JitKernel._check_range and JitKernel._check_ranges
      methods. We now check if a range is empty and if a well-formed
      global range was provided.
    • Minor fixes to error messages (typos, etc.)
    • Add missing docstrings to numba_dpex.core.exceptions classes.
  • Have you tested your changes locally for CPU and GPU devices?
  • Have you made sure that new changes do not introduce compiler warnings?

    - Removes superfluous copy inside JitKernel.__getitem__
    - Improves the JitKernel._check_range and JitKernel._check_ranges
      methods. We now check if a range is empty and if a well-formed
      global range was provided.
    - Minor fixes to error messages (typos, etc.)
    - Add missing docstrings to numba_dpex.core.exceptions classes.
@diptorupd diptorupd merged commit 9809c95 into main Jan 19, 2023
@diptorupd diptorupd deleted the fix/check_range branch January 19, 2023 04:32
github-actions bot added a commit that referenced this pull request Jan 19, 2023
Fixes to checking validity of a range. 9809c95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants