Test results for amd64, renoir, crypto_stream/trivium

[Page version: 20260302 15:53:32]

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

Computer: renoir
Microarchitecture: amd64; Zen 2 (860f01)
Architecture: amd64
CPU ID: AuthenticAMD-00860f01-178bfbff
SUPERCOP version: 20260217
Operation: crypto_stream
Primitive: trivium

Time	Object size	Test size	Implementation	Compiler	Benchmark date	SUPERCOP version
3997	2997 0 1	25752 1272 1504	`T:e/submissions/trivium`	`clang -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
4085	3492 0 1	28880 1272 1504	`T:e/submissions/trivium`	`clang -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
4087	3492 0 1	29480 1272 1536	`T:e/submissions/trivium`	`clang -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
4289	3224 0 4	25911 1200 1632	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
4294	3398 0 4	26871 1200 1632	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
4310	4520 0 4	30167 1200 1632	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
6685	2539 0 4	23971 1184 1600	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
9682	3377 0 1	28640 1272 1504	`T:e/submissions/trivium`	`clang -mcpu=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217
9782	2180 0 1	25446 1264 1568	`T:e/submissions/trivium`	`clang -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260221	20260217

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 (12.2.0)`