hyperscan fails to compile with gcc-10.1.0

[arkamar]

I cannot compile hyperscan with gcc-10.1.0. It fails with following error

[36/340] /usr/bin/gcc-10.1.0  -I. -I/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1 -I/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src -isystem /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/include  -pipe -march=native -mssse3 -mavx2  -O3 -std=c99 -Wall -Wextra -Wshadow -Wcast-qual -fno-strict-aliasing -Werror -Wno-array-bounds -Wno-maybe-uninitialized -Wno-abi -fno-omit-frame-pointer -Wvla -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes  -fPIC -MD -MT CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o -MF CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o.d -o CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o -c /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c
FAILED: CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o 
/usr/bin/gcc-10.1.0  -I. -I/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1 -I/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src -isystem /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/include  -pipe -march=native -mssse3 -mavx2  -O3 -std=c99 -Wall -Wextra -Wshadow -Wcast-qual -fno-strict-aliasing -Werror -Wno-array-bounds -Wno-maybe-uninitialized -Wno-abi -fno-omit-frame-pointer -Wvla -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes  -fPIC -MD -MT CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o -MF CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o.d -o CMakeFiles/hs_exec_shared.dir/src/rose/stream.c.o -c /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c
In file included from /usr/lib/gcc/x86_64-gentoo-linux-musl/10.1.0/include/immintrin.h:51,
                 from /usr/lib/gcc/x86_64-gentoo-linux-musl/10.1.0/include/x86intrin.h:32,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/util/intrinsics.h:59,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/util/simd_types.h:34,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/ue2common.h:78,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/hwlm/hwlm.h:36,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/catchup.h:51,
                 from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c:29:
In function ‘_mm256_storeu_si256’,
    inlined from ‘copy_upto_32_bytes’ at /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/util/simd_utils.h:610:5,
    inlined from ‘prepScanBuffer’ at /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream_long_lit.h:209:13,
    inlined from ‘storeLongLiteralState’ at /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream_long_lit.h:349:30,
    inlined from ‘ensureStreamNeatAndTidy’ at /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c:411:5,
    inlined from ‘roseStreamExec’ at /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c:676:9:
/usr/lib/gcc/x86_64-gentoo-linux-musl/10.1.0/include/avxintrin.h:928:8: error: writing 32 bytes into a region of size 24 [-Werror=stringop-overflow=]
  928 |   *__P = __A;
      |   ~~~~~^~~~~
In file included from /var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c:37:
/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream.c: In function ‘roseStreamExec’:
/var/tmp/portage/dev-libs/hyperscan-5.2.1-r2/work/hyperscan-5.2.1/src/rose/stream_long_lit.h:348:12: note: at offset 0 to object ‘tempbuf’ with size 24 declared here
  348 |         u8 tempbuf[LONG_LIT_HASH_LEN];
      |            ^~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.

[xiangwang1]

These are false positives generated by GCC-10 - our code logic guarantees that these situations won't happen. We'll work out a fix for this. Thanks.

[arkamar]

Thank you for fixing this in 5.3.0!