https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83462
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Target|arm-none-eabi |arm-none-eabi,
| |powerpc64*-linux
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-12-22
Depends on| |83543
Ever confirmed|0 |1
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed with an arm-none-eabi cross-compiler. The arm-none-eabi C++ results
show many more failures than the C results for the same test.
Today's test results show a FAIL and an XFAIL in both powerpc64 and
powerpc64le:
https://gcc.gnu.org/ml/gcc-testresults/2017-12/msg01429.html
https://gcc.gnu.org/ml/gcc-testresults/2017-12/msg01417.html
XPASS: c-c++-common/Warray-bounds-3.c -Wc++-compat strcpy (test for warnings,
line 362)
FAIL: c-c++-common/Warray-bounds-4.c -Wc++-compat (test for warnings, line
67)
I see slightly different results with the powerpc64le cross-compiler. At least
one problem is in the test itself not being prepared for GCC formatting char[5]
as 'char[5]' in C but as 'char [5]' in C++. It would be nice to fix this (in
GCC) and have both print arrays the same way. Until then, let me fix the test.
That will turn that FAIL into an XFAIL.
The Warray-bounds-4.c failure on line 67 is due to bug 83543.
I'm traveling until next weekend but I'll look into it after I get back.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83543
[Bug 83543] strlen of a local array member not optimized on some targets
