https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91457
--- Comment #13 from Martin Sebor <msebor at gcc dot gnu.org> --- (In reply to Christophe Lyon from comment #10) Yes, the warning is intended and Glibc was just patched to avoid it: https://sourceware.org/ml/glibc-cvs/2019-q3/msg00459.html (In reply to Iain Sandoe from comment #11) I haven't gone back to understand why r273783 makes the difference on hppa2.0w-hp-hpux11.11 and answer my question in comment #6. The warnings in this area (-Warray-bounds and the new -Wstringop-overflow for [multi]character assignments) are sensitive to subtle differences in the IL, which in turn seems to change from target to target depending on what the folder decides to transform the assignments to. As each warning is implemented differently and runs at part of a different pass, getting them to trigger consistently across all targets is like herding cats. Figuring out what the folder does on each target and parameterizing the tests on the variables that influence its decisions is also not trivial. Anyway, since this bug is specific to Warray-bounds-4.C on hppa2.0w-hp-hpux11.11, opening a searate issue for the Warray-bounds-8.C failures on Darwin might be best.
