Home
last modified time | relevance | path

Searched refs:W (Results 1 – 13 of 13) sorted by relevance

/rk3399_ARM-atf/lib/zlib/
H A Dcrc32.h59 #ifdef W
61 #if W == 8
211 #if W == 8
1749 #if W == 8
3287 #if W == 8
4825 #if W == 8
6363 #if W == 8
7901 #if W == 8
H A Dcrc32.c76 # define W Z_TESTW macro
80 # define W 8 /* required for MAKECRCH */ macro
83 # define W 8 macro
85 # define W 4 macro
89 #ifdef W
90 # if W == 8 && defined(Z_U8)
93 # undef W
94 # define W 4 macro
97 # undef W
102 #if defined(__aarch64__) && defined(__ARM_FEATURE_CRC32) && W == 8
[all …]
/rk3399_ARM-atf/plat/intel/soc/common/lib/sha/
H A Dsha.h65 static inline void LOAD_OP(int I, uint64_t *W, const uint8_t *input) in LOAD_OP() argument
67 GET_UINT64_BE(W[I], input, I*8); in LOAD_OP()
70 static inline void BLEND_OP(int I, uint64_t *W) in BLEND_OP() argument
72 W[I & 15] += s1(W[(I-2) & 15]) + W[(I-7) & 15] + s0(W[(I-15) & 15]); in BLEND_OP()
H A Dsha.c141 uint64_t W[16]; in sha512_transform() local
155 LOAD_OP(i + j, W, input); in sha512_transform()
158 BLEND_OP(i + j, W); in sha512_transform()
163 t1 = h + e1(e) + Ch(e, f, g) + sha512_K[i] + W[(i & 15)]; in sha512_transform()
165 t1 = g + e1(d) + Ch(d, e, f) + sha512_K[i+1] + W[(i & 15) + 1]; in sha512_transform()
167 t1 = f + e1(c) + Ch(c, d, e) + sha512_K[i+2] + W[(i & 15) + 2]; in sha512_transform()
169 t1 = e + e1(b) + Ch(b, c, d) + sha512_K[i+3] + W[(i & 15) + 3]; in sha512_transform()
171 t1 = d + e1(a) + Ch(a, b, c) + sha512_K[i+4] + W[(i & 15) + 4]; in sha512_transform()
173 t1 = c + e1(h) + Ch(h, a, b) + sha512_K[i+5] + W[(i & 15) + 5]; in sha512_transform()
175 t1 = b + e1(g) + Ch(g, h, a) + sha512_K[i+6] + W[(i & 15) + 6]; in sha512_transform()
[all …]
/rk3399_ARM-atf/make_helpers/
H A Ddefaults.mk14 W := 0
H A Dcflags.mk72 cflags-common += $(WARNING$(W))
/rk3399_ARM-atf/docs/process/
H A Dsecurity-hardening.rst133 - The ``W`` build flag can be used to enable a number of compiler warning
134 options to detect potentially incorrect code. TF-A is tested with ``W=0`` but
135 it is recommended to develop against ``W=2`` (which will eventually become the
H A Dcoding-guidelines.rst408 ``W`` build flag to ``W=3`` enables the *-Wpointer-arith* compiler flag and
/rk3399_ARM-atf/
H A DMakefile161 ifdef W
162 ifneq (${W},0)
735 W \
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-options.rst247 When specifying higher warnings levels (``W=1`` and higher), this option
250 contributions are still expected to build with ``W=0`` and ``E=1`` (the
1216 - ``W``: Warning level. Some compiler warning options of interest have been
1223 - ``W=0`` (default)
1230 - ``W=1``
1234 ``W=0`` builds (a few of the ``-Wextra`` additions). This level is expected
1235 to eventually be merged into ``W=0``. Some warnings are expected on some
1238 - ``W=2`` (recommended)
1242 into ``W=0``. Lots of warnings are expected, primarily from external
1246 - ``W=3``
/rk3399_ARM-atf/docs/plat/
H A Drcar-gen3.rst22 | R-Car M3-W | - Salvator-X | |
/rk3399_ARM-atf/docs/design/
H A Dfirmware-design.rst1842 overwrite BL1 R/W data and BL2. This implies that BL1 global variables
/rk3399_ARM-atf/docs/
H A Dchange-log.md11203 - Remove several warnings reported with W=2 and W=1
11475 - Warning levels are now selectable with `W=<1,2,3>`
11635 descriptors describing the list of executable images are created in BL2 R/W