Test results for amd64, saber214, crypto_sign/rainbowbinary256181212

[Page version: 20250427 16:08:48]

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: ...
usehash.cpp: usehash.cpp: In function 'int crypto_sign_rainbowbinary256181212_ref_timingleaks(unsigned char*, long long unsigned int*, const unsigned char*, long long unsigned int, const unsigned char*)':
usehash.cpp: usehash.cpp:39:16: warning: comparison of integer expressions of different signedness: 'int' and 'long long unsigned int' [-Wsign-compare]
usehash.cpp:    39 |   for (i = 0;i < mlen;++i) {
usehash.cpp:       |              ~~^~~~~~
usehash.cpp: usehash.cpp: In function 'int crypto_sign_rainbowbinary256181212_ref_timingleaks_open(unsigned char*, long long unsigned int*, const unsigned char*, long long unsigned int, const unsigned char*)':
usehash.cpp: usehash.cpp:59:30: warning: comparison of integer expressions of different signedness: 'int' and 'long long unsigned int' [-Wsign-compare]
usehash.cpp:    59 |   for (i = SIGNATURE_BYTES;i < smlen;++i) m[i - SIGNATURE_BYTES] = sm[i];
usehash.cpp:       |                            ~~^~~~~~~