Lines Matching +full:macos +full:- +full:arm

7 terminology *subclass*, *implementation*, or *type* [^footnote-1] to refer to a
27     - have an appended `_Private` (for example, `StashValues_Private`)
29     - have an appended `_Subtype` (for example, `MatMultSeq_AIJ`).
44 06. Each application-usable function begins with the name of the class
49 07. Functions that PETSc provides as defaults for user-providable
54     the word “set” or “get”, for example, `-ksp_gmres_restart`.
64 12. Use the abbreviation NaN for Not-a-Number.
71    is a signed 32-bit or 64-bit `int` depending on the `./configure` option
72    `--with-64-bit-indices`. There is the possibility of integer overflow with the
73    32-bit version.
75 2. `PetscCount` is `ptrdiff_t`, (on 64-bit systems it is 64-bits) and should be used for array size…
79    when these arrays get too large then `--with-64-bit-indices` must be used to
121 The `.clang-format` file in the PETSc root directory controls the white space and basic layout. You…
123 Even with the use of `clang-format` there are still many decisions about code formatting that must …
135 …nt arity (levels of indirection) are considered to be different types. `clang-format` automatically
197     The only exceptions to this rule are begin-end style macros which embed local variables
227 10. Do not leave sections of commented-out code or dead source code protected with `ifdef foo` in t…
230 …(`/*Do not do this*/`) for multi-line comments, and `// Comment` for single-line comments in sourc…
232 12. Do not put a `*` at the beginning or end of each line of a multi-line comment.
234 13. Do not use `/* ---- ... ----- */` or similar constructs to separate parts of source code files.
287                   + (vxp * (u - x[j][i - 1].omega) + vxm * (x[j][i + 1].omega - u)) * hy //
288                   + (vyp * (u - x[j - 1][i].omega) + vym * (x[j + 1][i].omega - u)) * hx //
289                   - .5 * grashof * (x[j][i + 1].temp - x[j][i - 1].temp) * hy;
292 17. The use of `// clang-format off` is allowed in the source code but should only be used when nec…
296     // clang-format off
298     // clang-format on
306     v1900+ (Visual Studio 2015). Examples of such banned features include variable-length arrays.
307     Note that variable-length arrays (including VLA-pointers) are not supported in C++ and
331     non-comment line of the file. There must be no leading or trailing empty (non-comment)
417 04. All public functions must sanity-check their arguments using the appropriate
451     The former usage allows syntax and type-checking in all configurations of
504     library for each top-level class (`Mat`, `Vec`, `KSP`, and so on), and that plugin
509     - `MatStashCreate_Private()` is marked `PETSC_INTERN` as it is used
511     - all functions, such as `KSPCreate()`, included in the public
513     - `VecLoad_Default()` is marked
575 - `/*@`
577 - `/*@C`
579 - `/*E`
582 - `/*S`
586 - `/*J`
590 - `/*MC`
594 directory `ftn-custom`, while those automatically generated
620 01. The item’s name, followed by a dash and brief (one-sentence)
630     - `Not Collective` if the function need not be called on multiple (or possibly all) MPI
632     - `Collective` if the function is a collective operation.
633     - `Logically Collective; yyy must contain common value]`
652     . arg - the integer argument description
663 10. (Optional) a `Note(s):` section containing in-depth discussion,
675 13. (If applicable) references should be indicated inline with \{cite}\`Bibtex-key\` where
676     Bibtex-key is in the file `doc/petsc.bib`, as in the manual page for `PCFIELDSPLIT`.
687 [^footnote-1]: Type also refers to the string name of the subclass.
700    The Apple computer operating system is written as macOS.
703 4. ARM is a family of processor designs, while Arm is the company that licenses them.