Lines Matching refs:backend

7 At runtime, the user can select the different backend implementations to target different hardware,…
11 …uld pass any computationally expensive or hardware specific operations to a backend implementation.
13 …backend specific implementation of the object, typically found in `/backends/[impl]/ceed-[impl]-[o…
14 …he interface or by the backends may be added to the backend API in the header `/include/ceed/backe…
24 A Ceed backend is not required to implement all libCeed objects or {ref}`CeedOperator` methods.
25 There are three mechanisms by which a Ceed backend can inherit implementations from another Ceed ba…
28 …Ceed` will provide the implementation of any libCeed objects that parent backend does not implemen…
29 …m/serial` backend implements the `CeedTensorContract` object itself but delegates all other functi…
32 …`Ceed` will only provide the implementation of that specific libCeed object for the parent backend.
36    The parent backend must implement the basic {ref}`CeedOperator` functionality.
37 …above, this fallback {ref}`Ceed` object should be created and set in the backend `CeedInit` functi…
38 …In order to use operator fallback, the parent backend and fallback backend must use compatible E-v…
45 There are 4 general 'families' of backend implementations.
46 … internal data layouts are specific to backend families, it is generally not possible to delegate …
51 This backend contains the basic implementations of most objects that other backends rely upon.
54 …u/self/ref/blockend` and `/cpu/self/opt/*` backends delegate to the `/cpu/self/ref/serial` backend.
55 The `/cpu/self/ref/blocked` backend updates the {ref}`CeedOperator` to use an E-vector and Q-vector…
57 This reduced the memory required to utilize this backend significantly.
68 The CUDA, HIP, and SYCL backend families all follow similar designs.
70 While the SYCL backend was based upon the CUDA and HIP backends, there are more internal difference…
91 …data layout (including never fully forming these vectors) so long as the backend passes the `t5**`…
104 …If the backend uses a strided E-vector layout, then the data for node `i`, component `j`, element …
105 …se and these tests will need to be marked as allowable failures for this backend in the test suite.
112 …s for a field with `emode` `CEED_EVAL_NONE` is properly ordered when the backend uses different la…
118 For any given precision and memory type, a backend should only have 'owned' or 'borrowed' memory, n…
246 …nting the current libCEED version number and a list of current available backend resources to `std…
293 #include <ceed/backend.h>