AdaptiveCpp / AdaptiveCpp/AdaptiveCpp
Implementation Plan of SYCL Image
- Lingua principale
- C++
- Stelle
- 1.9k
- Fork
- 228
- Merge medio
- 4g 1h
- PR unite (30g)
- 25
Descrizione
Many GPUs contain special optimizations for texture memory, originally meant for 3D graphics. This usually involves storing 2D or 3D data in a device-specific tiled format to increase its data locality. On some older GPUs, there also exists a separate texture cache (although this difference has been largely eliminated in newer GPUs). Also, one may also access some features specific to image processing. In OpenCL and SYCL, texture memory can be used via an Image object.
According to SYCL 2020,
> Memory objects in SYCL fall into one of two categories: buffer objects and image objects. A buffer object stores a one-, two- or three-dimensional collection of elements that are stored linearly directly back to back in the same way C or C++ stores arrays. An image object is used to store a one-, two- or three-dimensional texture, frame-buffer or image data that may be stored in an optimized and device-specific format in memory and must be accessed through specialized operations.
Currently, Image is not implemented in AdaptiveCpp. Is there any plan on the roadmap for implementing that in the future?
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.