https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
--- Comment #7 from Martin Sebor ---
You're welcome and no need to apologize. We want to improve the warnings (and
the rest of the compiler) and these reports help us understand both the
limitations and opportunities for improvements, or at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
--- Comment #6 from Josiah VanderZee
---
Thank you, I am grateful that you took your time to explain this so well. I am
sorry I opened a bug report without a deeper investigation into whether it was
definitely a bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
--- Comment #5 from Eric Gallager ---
(In reply to Martin Sebor from comment #4)
> Adding the following just before the definition of the string o prevents the
> warning. Another alternative is to make both length and the loop control
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
Martin Sebor changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
--- Comment #3 from Josiah VanderZee
---
Created attachment 51768
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51768=edit
Test case to reproduce strange -Wstringop-overflow warning
I'm worried this test case is too large to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176
Josiah VanderZee changed:
What|Removed |Added
URL||https://github.com/minetest
