Add paddle backend

[HydrogenSulfate]

Category

• New feature
• Bugfix
• Breaking change
• Refactoring
• Documentation
• Other (please explain)

Description

As talked in #285, we now add PaddlePaddle framework as one of backends.

run test:

# cu123
python -m pip install --pre paddlepaddle-gpu -i https://www.paddlepaddle.org.cn/packages/nightly/cu123/
# cu118
# python -m pip install --pre paddlepaddle-gpu -i https://www.paddlepaddle.org.cn/packages/nightly/cu118/
cd warp/
python warp/tests/test_paddle.py

output:

Warp 1.3.3 initialized:
   CUDA Toolkit 11.6, Driver 12.0
   Devices:
     "cpu"      : "x86_64"
     "cuda:0"   : "Tesla V100-PCIE-16GB" (16 GiB, sm_70, mempool enabled)
   Kernel cache:
     /root/.cache/warp/1.3.3
W0919 20:40:12.708083 18145 gpu_resources.cc:119] Please NOTE: device: 0, GPU Compute Capability: 7.0, Driver API Version: 12.0, Runtime API Version: 11.6
W0919 20:40:12.744881 18145 gpu_resources.cc:164] device: 0, cuDNN Version: 8.4.
test_array_ctype_from_paddle_cuda_0 (__main__.TestPaddle) ... ok
test_device_conversion_cuda_0 (__main__.TestPaddle) ... ok
test_direct_cuda_0 (__main__.TestPaddle) ... Module __main__ f49fde0 load on device 'cuda:0' took 673.95 ms  (compiled)
ok
test_dtype_from_paddle (__main__.TestPaddle) ... ok
test_dtype_to_paddle (__main__.TestPaddle) ... ok
test_from_paddle_cuda_0 (__main__.TestPaddle) ... ok
test_from_paddle_slices_cuda_0 (__main__.TestPaddle) ... ok
test_from_paddle_zero_strides_cuda_0 (__main__.TestPaddle) ... ok
test_paddle_autograd_cuda_0 (__main__.TestPaddle) ... ok
test_to_paddle_cuda_0 (__main__.TestPaddle) ... ok

----------------------------------------------------------------------
Ran 10 tests in 0.805s

OK

todolist:

• Add __cuda_array_interface__ in paddlepaddle([API] Add __cuda_array_interface__ for eager Tensor PaddlePaddle/Paddle#68192)
• Merge pr for supporting zero-copy dlpack([DLPACK] Support from_dlpack with shared memory PaddlePaddle/Paddle#67927)

Changelog

• Add specific line-by-line info of high level changes in this PR.

Before your PR is "Ready for review"

• Do you agree to the terms under which contributions are accepted as described in Section 9 the Warp License?
• Have you read the Contributor Guidelines?
• Have you written any new necessary tests?
• Have you added or updated any necessary documentation?
• Have you added any files modified by compiling Warp and building the documentation to this PR (.e.g. stubs.py, functions.rst)?
• Does your code pass ruff check and ruff format --check?

[HydrogenSulfate]

@mmacklin Can you help to review this code? Thanks :)

[shi-eric]

Hi @HydrogenSulfate, we are currently busy preparing for the 1.4 release so I don't think we can review your changes until after next week, but in the meantime, can you squash your changes down to a single commit? This is because the way we merge external contributions right now means that we can't squash it ourselves, or else your name disappears from the author list. Thanks!

[HydrogenSulfate]

Hi @HydrogenSulfate, we are currently busy preparing for the 1.4 release so I don't think we can review your changes until after next week, but in the meantime, can you squash your changes down to a single commit? This is because the way we merge external contributions right now means that we can't squash it ourselves, or else your name disappears from the author list. Thanks!

Thanks for reply, commits will be squashed in #318