Test results for amd64, kizomba, crypto_stream/trivium

[Page version: 20260113 15:48:17]

Measurements for amd64, kizomba, crypto_stream Test results for amd64, kizomba, crypto_stream Test results for crypto_stream/trivium

Computer: kizomba
Microarchitecture: amd64; Kaby Lake (906e9)
Architecture: amd64
CPU ID: GenuineIntel-000906e9-bfebfbff
SUPERCOP version: 20251222
Operation: crypto_stream
Primitive: trivium

Time	Object size	Test size	Implementation	Compiler	Benchmark date	SUPERCOP version
3312	2272 0 1	15151 828 968	`T:e/submissions/trivium`	`clang -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3327	2163 0 1	15984 820 1032	`T:e/submissions/trivium`	`clang -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3354	2767 0 4	16973 804 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3359	3285 0 1	20063 828 1032	`T:e/submissions/trivium`	`clang -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3361	3285 0 1	20143 828 1032	`T:e/submissions/trivium`	`clang -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3365	3871 0 4	20229 804 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3387	3131 0 1	18831 828 968	`T:e/submissions/trivium`	`clang -mcpu=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3484	2684 0 4	16444 796 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222
3628	2248 0 4	14864 780 1032	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260105	20251222

Compiler output

trivium.c: In file included from trivium.c:1:
trivium.c: e/trivium.c: In function 'crypto_stream_trivium_e_submissions_trivium_timingleaks_ECRYPT_keysetup':
trivium.c: e/trivium.c:210:8: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
trivium.c:   210 |     *s = key[i];
trivium.c:       |     ~~~^~~~~~~~
trivium.c: In file included from e/trivium.c:11:
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [32, 536870912] into destination object 'init' of size 16
trivium.c:    47 |   u64 init[2];
trivium.c:       |       ^~~~
trivium.c: e/ecrypt-sync.h:47:7: note: destination object 'init' of size 16
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [32, 536870912] into destination object 'init' of size 16
trivium.c: e/trivium.c:210:8: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
trivium.c:   210 |     *s = key[i];
trivium.c:       |     ~~~^~~~~~~~
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [33, 536870913] into destination object 'init' of size 16
trivium.c:    47 |   u64 init[2];
trivium.c:       |       ^~~~
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [1, 16] into destination object 'init' of size 16
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [33, 536870913] into destination object 'init' of size 16
trivium.c: e/trivium.c:210:8: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
trivium.c:   210 |     *s = key[i];
trivium.c:       |     ~~~^~~~~~~~
trivium.c: e/ecrypt-sync.h:47:7: note: at offset [34, 536870914] into destination object 'init' of size 16
trivium.c:    47 |   u64 init[2];
trivium.c:       |       ^~~~
trivium.c: ...

Number of similar (implementation,compiler) pairs: 1, namely:

Implementation	Compiler
`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (13.3.0)`