[Bug tree-optimization/107087] [13 Regression] bits/stl_algobase.h:431: warning: 'void* __builtin_memcpy(void*, const void*, unsigned int)' reading between 8 and 2147483644 bytes from a region of size 4 [-Wstringop-overread]

redi at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Mar 30 08:31:21 GMT 2023


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107087

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> Comment 0 comes from 22_locale/money_put/cons/3.cc
> 
> make check RUNTESTFLAGS="conformance.exp=22_locale/money_put/cons/3.cc
> --target_board=unix/-m32"
> 
> (but I don't see it failing now).

I was using the wrong flags, with -m32 -D_GLIBCXX_DEBUG it fails on gcc-12:

Schedule of variations:
    unix/-m32/-D_GLIBCXX_USE_CXX11_ABI=0

Running target unix/-m32/-D_GLIBCXX_USE_CXX11_ABI=0
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/jwakely/src/gcc/gcc-12/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/home/jwakely/src/gcc/gcc-12/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
FAIL: 22_locale/money_get/cons/3.cc (test for excess errors)
FAIL: 22_locale/money_put/cons/3.cc (test for excess errors)


And also still fails on trunk after r13-6905:

Schedule of variations:
    unix/-m32/-D_GLIBCXX_USE_CXX11_ABI=0

Running target unix/-m32/-D_GLIBCXX_USE_CXX11_ABI=0
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
FAIL: 22_locale/money_get/cons/3.cc (test for excess errors)
FAIL: 22_locale/money_put/cons/3.cc (test for excess errors)


Comment 1 is fixed on trunk now though, thanks.


More information about the Gcc-bugs mailing list