Test results for amd64, h9ivy, crypto_stream/trivium

[Page version: 20250926 22:04:25]

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

Computer: h9ivy
Microarchitecture: amd64; Ivy Bridge+AES (306a9)
Architecture: amd64
CPU ID: GenuineIntel-000306a9-bfebfbff
SUPERCOP version: 20250922
Operation: crypto_stream
Primitive: trivium

Time	Object size	Test size	Implementation	Compiler	Benchmark date	SUPERCOP version
2888	2619 0 4	15659 772 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3019	2733 0 4	15956 780 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3040	3805 0 4	18412 780 1064	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3068	2082 0 4	13663 756 1032	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3078	3131 0 1	22309 820 968	`T:e/submissions/trivium`	`clang -mcpu=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3087	3323 0 1	20573 820 968	`T:e/submissions/trivium`	`clang -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3088	3323 0 1	20109 820 968	`T:e/submissions/trivium`	`clang -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3105	2256 0 1	14997 820 968	`T:e/submissions/trivium`	`clang -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415
3120	2167 0 1	14774 812 968	`T:e/submissions/trivium`	`clang -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20250826	20250415

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