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

--- Comment #6 from seurer at gcc dot gnu.org ---
Note that I am still seeing these failures though the Warray-bounds-3.c ones
are working now,

FAIL: c-c++-common/Warray-bounds-4.c  -Wc++-compat   (test for warnings, line
67)
FAIL: c-c++-common/Warray-bounds-4.c  -std=gnu++11  (test for warnings, line
67)
FAIL: c-c++-common/Warray-bounds-4.c  -std=gnu++14  (test for warnings, line
67)
FAIL: c-c++-common/Warray-bounds-4.c  -std=gnu++98  (test for warnings, line
67)

spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-trunk/gcc/xgcc
-B/home/seurer/gcc/build/gcc-trunk/gcc/
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -Wc++-compat -O2
-Warray-bounds=2 -Wno-stringop-overflow -ftrack-macro-expansion=0 -S -o
Warray-bounds-4.s
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c: In
function 'test_memcpy_bounds_memarray_range':
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c:47:3:
warning: 'memcpy' offset [6, 8] from the object at 'ma' is out of the bounds of
referenced subobject 'a5' with type 'char[5]' at offset 0 [-Warray-bounds]
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c:48:3:
warning: 'memcpy' offset [6, 10] from the object at 'ma' is out of the bounds
of referenced subobject 'a5' with type 'char[5]' at offset 0 [-Warray-bounds]
output is:
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c: In
function 'test_memcpy_bounds_memarray_range':
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c:47:3:
warning: 'memcpy' offset [6, 8] from the object at 'ma' is out of the bounds of
referenced subobject 'a5' with type 'char[5]' at offset 0 [-Warray-bounds]
/home/seurer/gcc/gcc-trunk/gcc/testsuite/c-c++-common/Warray-bounds-4.c:48:3:
warning: 'memcpy' offset [6, 10] from the object at 'ma' is out of the bounds
of referenced subobject 'a5' with type 'char[5]' at offset 0 [-Warray-bounds]

Reply via email to