Implementation notes: amd64, saber214, crypto_sign/rainbowbinary256181212
Computer: saber214
Microarchitecture: amd64; Bulldozer (600f20)
Architecture: amd64
CPU ID: AuthenticAMD-00600f20-1789c3f5
SUPERCOP version: 20240808
Operation: crypto_sign
Primitive: rainbowbinary256181212
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) |