Lines Matching refs:in
13 in the root of the repository: ``.editorconfig``. With a supported editor, the
14 rules set out in this file can be automatically applied when you are editing
15 files in the |TF-A| repository.
17 Several editors include built-in support for EditorConfig files, and many others
29 source tree. The project also defines certain *checkpatch* options in the
30 ``.checkpatch.conf`` file in the top-level directory.
39 in the `Linux master tree`_ *scripts* directory, then set the ``CHECKPATCH``
40 environment variable to point to ``checkpatch.pl`` (with the other 2 files in
61 Some checkpatch warnings in the TF codebase are deliberately ignored. These
65 generally conform to the 80 character limit this is overly restrictive in some
146 This allows the linker to put the data in a read-only data section instead of a
147 writeable data section, which may result in a smaller and faster binary. Note
148 that this may require dependent functions (``init()`` in the above example) to
169 | ``snprintf`` | Caution | ensure result fits in buffer |
173 | | | specified in format string |
184 The `libc` component in the codebase will not add support for the banned APIs.
213 If ``MY_STRUCT_SIZE`` in the above example were wrong then the compiler would
227 image is provided by multiple entities. This allows us to be more aggressive in
230 This is in contrast to code in a Linux environment, which is less tightly
255 images in order to check if asserts are firing. For example, the release variant
258 always take action, even in release builds.
289 error. This situation should be handled in one of the following ways:
294 2. If the unrecoverable error is expected to occur in certain circumstances,
299 ``plat_panic_handler`` and ``plat_error_handler`` in the same way (for example,
333 the system from executing in this state indefinitely.
339 - A Trusted OS is waiting for a response from a proxy in the normal world that
344 Use of built-in *C* and *libc* data types
351 - Where possible, use the built-in *C* data types for variable storage (for
354 data stored, which the built-in *C* types guarantee.
356 - Avoid using the exact-size standard *C99* types in general (for example,
359 for example to represent data of a known structure. When using them in struct
360 definitions, consider how padding in the struct will work across architectures.
361 For example, extra padding may be introduced in |AArch32| systems if a struct
369 - Avoid use of ``short`` as this may end up being slower than ``int`` in some
388 - If an argument in a function declaration is pointing to a known type then
391 - If a variable (including an argument in a function declaration) is pointing
394 ``uintptr_t``. This will reduce the amount of casting required in the code.
398 - For other pointer arguments in a function declaration, use ``void *``. This
417 code in case of error. This practice should be used sparingly.
420 in its native size (32-bit in |AArch32| and 64-bit in |AArch64|). This is not a
421 standard *C99* type but is widely available in libc implementations,
424 example, the following struct in ``ep_info.h`` could use this type to minimize
448 Generally, prefer code written in C over assembly. Assembly code is less