Test results for amd64, alder, crypto_stream/trivium

[Page version: 20260312 23:06:37]

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

Computer: alder
Microarchitecture: amd64; Golden Cove (90675-00)
Architecture: amd64
CPU ID: GenuineIntel-00090675-00-bfebfbff
SUPERCOP version: 20260217
Operation: crypto_stream
Primitive: trivium

Time	Object size	Test size	Implementation	Compiler	Benchmark date	SUPERCOP version
3237	2082 0 4	23434 1176 1640	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3238	2693 0 4	25991 1200 1672	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3239	3717 0 4	29495 1200 1672	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3299	2272 0 1	24760 1240 1544	`T:e/submissions/trivium`	`clang -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3318	2163 0 1	25293 1232 1608	`T:e/submissions/trivium`	`clang -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3321	3285 0 1	29947 1240 1608	`T:e/submissions/trivium`	`clang -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3363	3285 0 1	29899 1240 1608	`T:e/submissions/trivium`	`clang -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3373	3131 0 1	28400 1240 1544	`T:e/submissions/trivium`	`clang -mcpu=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20260302	20260217
3380	2619 0 4	25494 1192 1672	`T:e/submissions/trivium`	`gcc -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall`	20260302	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 (14.2.0)`