[Bug middle-end/117376] Spammy -Wstringop-overflow output with memcpy

2024-11-01 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117376 --- Comment #3 from Sam James --- (In reply to Andrew Pinski from comment #2) > I suspect there are some missing auto_diagnostic_group usage in > gimple-array-bounds.cc > gimple-ssa-warn-access.cc > pointer-query.cc > tree-ssa-strlen.cc Let me

[Bug middle-end/117376] Spammy -Wstringop-overflow output with memcpy

2024-11-01 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117376 --- Comment #2 from Andrew Pinski --- I suspect there are some missing auto_diagnostic_group usage in gimple-array-bounds.cc gimple-ssa-warn-access.cc pointer-query.cc tree-ssa-strlen.cc

[Bug middle-end/117376] Spammy -Wstringop-overflow output with memcpy

2024-11-01 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117376 --- Comment #1 from Andrew Pinski --- I think there is a missing check to see if the warning was emitted before the inform. I have seen the "note: destination object" diagnostic without a warning before too.