`dtype` parameter, and `from_ndarray` crash

Open
#269 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reproducing the dtype parameter and from_ndarray crashes on Fedora 40 with the Mesa/Rusticl OpenCL backend, then compare behavior with ROCm. Trace the two entry points and narrow down the backend-specific failure; done means both operations work without a segmentation fault on the reported setup.

Written by the indexing model from the issue text.

Description

I have a back end using mesa/rusticl OpenCL on fedora 40 with both an NVIDIA and AMD GPU. There are two opencl backends for the AMD device, ROCm and the aforementioned mesa drivers. The mesa drivers are how I interface to the NVIDIA GPU (trying to avoid using the proprietary driver). Everything works fine with the ROCm driver, however, any time there is a dtype parameter arrayfire segfaults, also I noticed it crashes with from_ndarray

Dominant language
Python
Stars
422
Forks
63
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arrayfire/arrayfire-python

All issues in arrayfire/arrayfire-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.