arrayfire / arrayfire/arrayfire

Generalize strides

Offen
#1,381 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
feature internal
Vorherrschende Sprache
C++
Sterne
4.9k
Forks
555
Ø Merge
1 Std. 24 Min.
Gemergte PRs (30 T.)
1

Beschreibung

**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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.