Test results for amd64, kizomba, crypto_stream/trivium

[Page version: 20260312 23:14:11]

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: 20260217
Operation: crypto_stream
Primitive: trivium
TimeObject sizeTest sizeImplementationCompilerBenchmark dateSUPERCOP version
33393285 0 130093 1256 1608T:e/submissions/triviumclang -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33513285 0 129837 1256 1608T:e/submissions/triviumclang -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33522767 0 427429 1224 1672T:e/submissions/triviumgcc -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33532272 0 125386 1256 1544T:e/submissions/triviumclang -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33582163 0 125908 1248 1608T:e/submissions/triviumclang -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33593871 0 431069 1224 1672T:e/submissions/triviumgcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
33823131 0 129026 1256 1544T:e/submissions/triviumclang -mcpu=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
34822684 0 426804 1216 1672T:e/submissions/triviumgcc -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall2026030320260217
36322248 0 425136 1200 1640T:e/submissions/triviumgcc -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall2026030320260217

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:
ImplementationCompiler
T:e/submissions/triviumgcc -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (13.3.0)