Test results for amd64, hertz, crypto_aead/aes128n12t8silcv3

[Page version: 20260219 16:18:58]

Compiler output

encrypt.c: encrypt.c:111:9: warning: unused variable 'j' [-Wunused-variable]
encrypt.c:   111 |     int j;
encrypt.c:       |         ^
encrypt.c: 1 warning generated.

Compiler output

encrypt.c: encrypt.c: In function 'crypto_aead_aes128n12t8silcv3_aesni_timingleaks_encrypt':
encrypt.c: encrypt.c:111:9: warning: unused variable 'j' [-Wunused-variable]
encrypt.c:   111 |     int j;
encrypt.c:       |         ^

Compiler output

encrypt.c: encrypt.c:70:2: warning: misleading indentation; statement is not part of the previous 'for' [-Wmisleading-indentation]
encrypt.c:    70 |         return RETURN_SUCCESS;
encrypt.c:       |         ^
encrypt.c: encrypt.c:65:5: note: previous statement is here
encrypt.c:    65 |     for(i = 0; i < CRYPTO_ABYTES; i++)
encrypt.c:       |     ^
encrypt.c: 1 warning generated.

Compiler output

encrypt.c: encrypt.c: In function 'crypto_aead_aes128n12t8silcv3_ref_timingleaks_decrypt':
encrypt.c: encrypt.c:65:5: warning: this 'for' clause does not guard... [-Wmisleading-indentation]
encrypt.c:    65 |     for(i = 0; i < CRYPTO_ABYTES; i++)
encrypt.c:       |     ^~~
encrypt.c: encrypt.c:70:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'for'
encrypt.c:    70 |         return RETURN_SUCCESS;
encrypt.c:       |         ^~~~~~

Namespace violations

encrypt.o AES128_KeyExpansion T
encrypt.o load_partial_block T
encrypt.o print_state T
encrypt.o roundkeys B
encrypt.o store_partial_block T
encrypt.o xor_length T

Namespace violations

aes_core.o AES_decrypt T
aes_core.o AES_encrypt T
aes_core.o AES_set_decrypt_key T
aes_core.o AES_set_encrypt_key T
aes_core.o print_state T
silc.o ae_encrypt T
silc.o ae_init T
silc.o process_ad T
utils.o print_cxt T
utils.o pstate T
utils.o pstate2 T
utils.o xor_bytes T
utils.o xor_bytes2 T