[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 Richard Biener changed: What|Removed |Added Target Milestone|10.2|10.3 --- Comment #5 from Richard

[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 Richard Biener changed: What|Removed |Added Target Milestone|--- |10.2 Priority|P3

[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 --- Comment #4 from Martin Sebor --- No. GCC's manual recommends using either flexible array members or zero-length arrays, and explicitly discourages abuses of arrays of length one (nothing is said about any such exceptions for larger arrays):

[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 --- Comment #3 from Jakub Jelinek --- The warning should change, not the conservative assumption. There is a lot of code in the wild with such trailing arrays, not everything uses flexible array members, [0] or [1] for that.

[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords|