arrayfire / arrayfire/arrayfire
Generalize strides
Open
feature
internal
- Dominant language
- C++
- Stars
- 4.9k
- Forks
- 555
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 1
Description
**Pros**:
`no-op` in the following statements refers to no kernel launch. it would require some changes to meta-data.
- `transpose` and `reorder` are now no-ops (we can have an additional parameter if we want to force copies).
- All indexing is now a no-op.
- `wrap` and `unwrap` can be no-ops in a few cases and would not require additional memory.
- `tile` can be a no-op without additional memory.
**Cons**:
- Most of kernels are based on the assumption that the first dimension is contiguous, would require a lot of code changes.
- Even if we change kernels, it might create performance drops.
- Creating new bugs.
Contributor guide
Assessment
This issue has not been assessed yet.