Skip to content

Conversation

@umar456
Copy link
Member

@umar456 umar456 commented Jan 1, 2023

Changes to support CUDA 12

Description

  • Remove deprecated cuSPARSE API
  • Move all internal namespaces in the arrayfire namespace
  • Add Version class to support multiple versions of loaded libraries
  • Add support for sparse arrays in ASSERT_ARRAYS_* test macros

Fixes #3353 #3354

Changes to Users

  • Compile ArrayFire with CUDA 12
  • Currently CUDA 10 support is removed because of C++17 changes.

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • Functions added to unified API
  • Functions documented

There were some conflicts in the new cuda and oneapi version. This needed to be
done because the namespaces we used can conflict with other libraries.
@umar456 umar456 force-pushed the cuda12 branch 7 times, most recently from dfa6059 to 5661ffa Compare January 3, 2023 01:40
@umar456 umar456 force-pushed the cuda12 branch 3 times, most recently from 863e70f to 489ae22 Compare January 3, 2023 13:23
syurkevi
syurkevi previously approved these changes Jan 3, 2023
@umar456 umar456 merged commit b6f234e into arrayfire:master Jan 10, 2023
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.

[BUG] CU_CHECK does not check for validity of CUDA messages extracted from error code

2 participants