Test results for amd64, h8atom, crypto_sign/rainbowbinary256181212

[Page version: 20240912 08:39:10]

Measurements for amd64, h8atom, crypto_sign Test results for amd64, h8atom, crypto_sign Test results for crypto_sign/rainbowbinary256181212

Computer: h8atom
Microarchitecture: amd64; Bonnell (30661)
Architecture: amd64
CPU ID: GenuineIntel-00030661-bfebfbff
SUPERCOP version: 20240909
Operation: crypto_sign
Primitive: rainbowbinary256181212

Time	Object size	Test size	Implementation	Compiler	Benchmark date	SUPERCOP version
231189	30745 168 8	50396 1064 1568	`T:ref`	`clang++ -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20240709	20240625
232428	35369 168 8	56252 1064 1568	`T:ref`	`clang++ -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20240709	20240625
256921	28458 168 8	46091 1056 1568	`T:ref`	`clang++ -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20240709	20240625
269087	29096 168 8	47628 1064 1568	`T:ref`	`clang++ -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall`	20240709	20240625

Compiler output

rainbow-test.cpp: In file included from rainbow-test.cpp:1:
rainbow-test.cpp: ./gf.h:171:46: warning: while loop has empty body [-Wempty-body]
rainbow-test.cpp:                 if( M==n_read ) { while( ttt.set(fp)==16 ) ; break; }
rainbow-test.cpp:                                                            ^
rainbow-test.cpp: ./gf.h:171:46: note: put the semicolon on a separate line to silence this warning
rainbow-test.cpp: 1 warning generated.

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

Implementation	Compiler
`T:ref`	`clang++ -march=native -O2 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall (Ubuntu_Clang_14.0.0)`
`T:ref`	`clang++ -march=native -O3 -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall (Ubuntu_Clang_14.0.0)`
`T:ref`	`clang++ -march=native -O -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall (Ubuntu_Clang_14.0.0)`
`T:ref`	`clang++ -march=native -Os -fwrapv -Qunused-arguments -fPIC -fPIE -gdwarf-4 -Wall (Ubuntu_Clang_14.0.0)`

Compiler output

rainbow-test.cpp: In file included from gf.h:181,
rainbow-test.cpp:                  from rainbow-test.cpp:1:
rainbow-test.cpp: gf16.h: In member function 'void gfv_unit<p>::dump(FILE*) const [with unsigned int p = 16; FILE = FILE]':
rainbow-test.cpp: gf16.h:305:9: warning: this 'for' clause does not guard... [-Wmisleading-indentation]
rainbow-test.cpp:   305 |         for(unsigned i=0;i<N;i++) fprintf(fp,"%02X ",(int)((*this)[i].v)); fprintf(fp,"\n");
rainbow-test.cpp:       |         ^~~
rainbow-test.cpp: gf16.h:305:76: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'for'
rainbow-test.cpp:   305 |         for(unsigned i=0;i<N;i++) fprintf(fp,"%02X ",(int)((*this)[i].v)); fprintf(fp,"\n");
rainbow-test.cpp:       |                                                                            ^~~~~~~
rainbow-test.cpp: rainbow-test.cpp: In function 'int signatureofshorthash(unsigned char*, long long unsigned int*, const unsigned char*, long long unsigned int, const unsigned char*, long long unsigned int)':
rainbow-test.cpp: rainbow-test.cpp:56:15: warning: 'void* memcpy(void*, const void*, size_t)' writing to an object of type 'struct gfv<256, 24>' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
rainbow-test.cpp:    56 |         memcpy( &y , h ,M );
rainbow-test.cpp:       |         ~~~~~~^~~~~~~~~~~~~
rainbow-test.cpp: In file included from rainbow-test.cpp:1:
rainbow-test.cpp: gf.h:113:8: note: 'struct gfv<256, 24>' declared here
rainbow-test.cpp:   113 | struct gfv
rainbow-test.cpp:       |        ^~~
rainbow-test.cpp: rainbow-test.cpp: In function 'int verification(const unsigned char*, long long unsigned int, const unsigned char*, long long unsigned int, const unsigned char*, long long unsigned int)':
rainbow-test.cpp: rainbow-test.cpp:81:15: warning: 'void* memcpy(void*, const void*, size_t)' writing to an object of type 'struct gfv<256, 42>' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
rainbow-test.cpp:    81 |         memcpy( &x , sm ,N );
rainbow-test.cpp:       |         ~~~~~~^~~~~~~~~~~~~~
rainbow-test.cpp: In file included from rainbow-test.cpp:1:
rainbow-test.cpp: gf.h:113:8: note: 'struct gfv<256, 42>' declared here
rainbow-test.cpp:   113 | struct gfv
rainbow-test.cpp:       |        ^~~
rainbow-test.cpp: ...

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

Implementation	Compiler
`T:ref`	`g++ -march=native -mtune=native -O2 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (11.4.0)`
`T:ref`	`g++ -march=native -mtune=native -O3 -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (11.4.0)`
`T:ref`	`g++ -march=native -mtune=native -O -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (11.4.0)`
`T:ref`	`g++ -march=native -mtune=native -Os -fwrapv -fPIC -fPIE -gdwarf-4 -Wall (11.4.0)`