Lines Matching full:with

12 A new method for the associated libCEED object can be added in `/include/ceed-impl.h`, with a corre…
50 The basic CPU with the simplest implementation is `/cpu/self/ref/serial`.
63 These backends replace many of the implementations with methods that include more verification chec…
69 The CUDA and HIP backends are very similar, with minor differences.
112 …st take special care to ensure that the data in the Q-vectors for a field with `emode` `CEED_EVAL_…
124 Some checks for consistency and data validity with {ref}`CeedVector` array access are performed at …
129 …access to borrowed memory is set with {c:func}`CeedVectorSetArray` with `copy_mode = CEED_USE_POIN…
130 …The user must first call {c:func}`CeedVectorSetArray` with `copy_mode = CEED_USE_POINTER` for the …
135 …g {c:func}`CeedVectorSetValue` or by calling {c:func}`CeedVectorSetArray` with `copy_mode = CEED_C…
136 …- Owned memory can be set by calling {c:func}`CeedVectorSetArray` with `copy_mode = CEED_OWN_POINT…
212 …or example, a `CeedOperator` as its first argument, then it should be prefixed with `CeedOperator`.
230 4. All functions must start with a single blank line after the local variable declarations.
233 …ariables must be declared at the beginning of the code block (C90 style), never mixed in with code.
237    The block should begin with `/**` and end with `**/`, each on their own line.
246 …Note: Prefixing the resource with "help:" (e.g. "help:/cpu/self") will result in @ref CeedInt() pr…
260 …, i.e. those used in tests or examples, must have their *declarations* prefixed with `CEED_EXTERN`.
261     All other functions should have their *declarations* prefixed with `CEED_INTERN`.
288 Header files should be listed in alphabetical order, with installed headers preceding local headers…