Home
last modified time | relevance | path

Searched refs:backend (Results 1 – 25 of 32) sorted by relevance

12

/libCEED/tests/
H A Dt002-ceed.c9 const char *backend = argv[1]; in main() local
12 CeedInit(backend, &ceed); in main()
17 const bool is_exact_match = strcmp(resource, backend) == 0; in main()
18 …h_query_arguments = !is_exact_match && memcmp(resource, backend, resource_length) == 0 && backend[… in main()
20 …rguments) return CeedError(ceed, 1, "Incorrect full resource name: %s != %s\n", resource, backend); in main()
H A Djunit_common.py172 def post_test_hook(self, test: str, spec: TestSpec, backend: str) -> None:
504 def diff_ascii(test_file: Path, true_file: Path, backend: str) -> str:
514 tmp_backend: str = backend.replace('/', '-')
524 backend: str, test: str, index: int, verbose: bool) -> str:
585 def run_test(index: int, test: str, spec: TestSpec, backend: str,
606 run_args[run_args.index('{ceed_resource}')] = backend
609 run_args[i] = arg.replace('{ceed_resource}', backend.replace('/', '-'))
616 skip_reason: Optional[str] = suite_spec.check_pre_skip(test, spec, backend, nproc)
654 suite_spec.post_test_hook(test, spec, backend)
658 … skip_reason: Optional[str] = suite_spec.check_post_skip(test, spec, backend, test_case.stderr)
[all …]
/libCEED/doc/sphinx/source/api/
H A Dindex.rst48 These functions are intended to be used by backend developers of libCEED and can
49 generally be found in `ceed-backend.h`.
53 backend/Ceed
54 backend/CeedVector
55 backend/CeedElemRestriction
56 backend/CeedBasis
57 backend/CeedQFunction
58 backend/CeedOperator
/libCEED/benchmarks/
H A Dbenchmark.sh219 for backend in $backend_list; do
229 short_backend=${backend//[\/]}
237 echo "Using backend $backend ..." | tee $output_file
307 ceed=$backend
324 echo "Sub-shell for backend '$backend' returned error code $?. Stop."
H A Dpostprocess_plot.py77 backend = row['backend'] variable
82 pl_runs = sel_runs[(sel_runs.backend == backend) |
89 backend, num_nodes, num_procs))
158 num_procs_node, backend, backend_memtype, test_short), fontsize=16)
178 short_backend = backend.replace('/', '')
H A Dpostprocess_base.py22 backend='unknown',
/libCEED/doc/sphinx/source/
H A DlibCEEDdev.md7 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.
[all …]
H A Dreleasenotes.md102 - OCCA backend updated to latest OCCA release; DPC++ and OMP OCCA modes enabled.
103 …e OCCA parser, typedefs are required to use pointers to arrays in QFunctions with the OCCA backend.
133 …red` and `/gpu/cuda/gen` as well as `/gpu/hip/shared` and `/gpu/hip/gen` backend to improve mainta…
166 - Warning added when compiling OCCA backend to alert users that this backend is experimental.
167 - `ceed-backend.h`, `ceed-hash.h`, and `ceed-khash.h` removed. Users should use `ceed/backend.h`, `…
187 - Added support for non-tensor $H(\text{div})$ elements, to include CPU backend implementations and…
195 - Create backend constant `CEED_FIELD_MAX` to reduce magic numbers in codebase.
223 …ckends have been removed. These backends were intially added to test the backend inheritance mecha…
261 - Replace various uses of {code}`Ceed*Get*Status` with {code}`Ceed*Is*` in the backend API to match…
273 - New HIP backend: `/gpu/hip/ref`.
[all …]
H A DlibCEEDapi.md191 …\bm{\bm{\mathcal{E}}}$, $\bm{B}$, and $\bm{D}$ and the library provides *backend* implementations …
197 Flow of data through vector types inside libCEED Operators, through backend implementations of $\bm…
203 It also enables backend developers to impact many applications from a single implementation.
205 Our long-term vision is to include a variety of backend implementations in libCEED, ranging from re…
206 A simple reference backend implementation is provided in the file
213 (A backend may choose to operate incrementally without forming explicit **E-** or **Q-vectors**.)
245 The resource is used to locate a suitable backend which will have discretion over the implementatio…
400 `CeedInit` uses this prefix to find an appropriate backend for the resource.
/libCEED/backends/sycl/
H A Dceed-sycl-compile.sycl.cpp88 auto lz_context = sycl::get_native<sycl::backend::ext_oneapi_level_zero>(sycl_context); in CeedLoadModule_Sycl()
89 auto lz_device = sycl::get_native<sycl::backend::ext_oneapi_level_zero>(sycl_device); in CeedLoadModule_Sycl()
116 …*sycl_module = new SyclModule_t(sycl::make_kernel_bundle<sycl::backend::ext_oneapi_level_zero, syc… in CeedLoadModule_Sycl()
150 …ze_module_handle_t lz_module = sycl::get_native<sycl::backend::ext_oneapi_level_zero>(*sycl_module… in CeedGetKernel_Sycl()
160 …*sycl_kernel = new sycl::kernel(sycl::make_kernel<sycl::backend::ext_oneapi_level_zero>({*sycl_mod… in CeedGetKernel_Sycl()
/libCEED/backends/magma/tuning/
H A DREADME.md3 The `magma` backend uses specialized GPU kernels for a non-tensor basis with
25 specifies the backend to use, typically one of `/gpu/cuda/magma` or
29 the basis application for a given backend. Run `make tuning` from this directory
H A Dgenerate_tuning.py22 def benchmark(nb, build_cmd, backend, log): argument
31 ("hipDeviceSynchronize()" if "hip" in backend else "cudaDeviceSynchronize()"),
/libCEED/
H A Dpyproject.toml3 build-backend = "setuptools.build_meta"
H A DREADME.md198 A 'development' or 'debugging' version of Valgrind with headers is required to use this backend.
199 This backend can be run in serial or blocked mode and defaults to running in the serial mode if `/c…
/libCEED/julia/LibCEED.jl/gen/
H A Dgenerator.jl6 header_files = ["ceed.h", "ceed/cuda.h", "ceed/backend.h"]
/libCEED/examples/python/
H A Dtutorial-0-ceed.ipynb79 "To use a particular backend, for instance `/cpu/self/opt/blocked` you can specify"
95 …"Similarly, if libCEED is built with GPU support, you can specify a GPU backend, e.g., `/gpu/hip` …
H A Dtutorial-2-elemrestriction.ipynb200 …"* In the following example (intended for backend developers), we illustrate the creation of a blo…
270 …"* In the following example (intended for backend developers), we illustrate the creation and appl…
/libCEED/rust/libceed/
H A DREADME.md39 The resource string passed to `Ceed::init` is used to identify the "backend", which includes algori…
/libCEED/julia/LibCEED.jl/src/
H A DCeed.jl83 Returns true if backend of the given [`Ceed`](@ref) object is deterministic, and false
H A DGlobals.jl130 Indicate that the stride is determined by the backend.
H A DUserQFunction.jl99 "libCEED.jl.\nPlease use a different backend, for example: /gpu/cuda/shared ",
122 "loaded.\nThe libCEED backend is: $(getresource(ceed))\n",
H A DQFunction.jl45 "In order to use user Q-functions with a CUDA backend, the CUDA.jl package ",
H A DCeedVector.jl122 applicable. The backend may copy values to a different [`MemType`](@ref). See also
/libCEED/examples/nek/
H A DREADME.md48 -c|-ceed Ceed backend to be used for the run (optional, default: /cpu/self)
/libCEED/doc/papers/joss/
H A Dpaper.md141 \autoref{fig:libCEEDBackends} shows a subset of the backend implementations (backends) available in…
151 …using the \texttt{xsmm/blocked} backend on a 2-socket AMD EPYC 7452 (32-core, 2.35GHz) and the \te…
165 …MFEM users can pass `-d ceed-cuda:/gpu/cuda/gen` to use a `libCEED` CUDA backend, and similarly fo…

12