https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
Tobias Burnus changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #16 from Martin Sebor ---
I would expect r280041 to suppress the warnings but I haven't tested it.
Thomas or Tobias, can one of you please verify they are gone and resolve the
bug if appropriate?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #15 from Martin Sebor ---
Author: msebor
Date: Thu Jan 9 11:59:41 2020
New Revision: 280041
URL: https://gcc.gnu.org/viewcvs?rev=280041=gcc=rev
Log:
PR middle-end/93200 - spurious -Wstringop-overflow due to assignment
vectorization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
Richard Biener changed:
What|Removed |Added
Version|unknown |10.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #14 from Martin Sebor ---
(In reply to Tobias Burnus from comment #12)
The warnings have been enabled by default since _FORTIFY_SOURCE (and Builtin
Size Checking) was introduced. Given their severity I don't think we want
consider
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #13 from Martin Sebor ---
(In reply to Jakub Jelinek from comment #9)
Thanks for the nice test case! The assumptions the warning makes aren't
accidental: it tries to detect bugs that would otherwise go undetected, and it
relies on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #12 from Tobias Burnus ---
(In reply to Martin Sebor from comment #11)
> Because like all flow-based warnings, -Wstringop-overflow has a non-zero rate
> of false positives
I think false positive is okay fine, but the question is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92956
--- Comment #11 from Martin Sebor ---
Here's some history. When -Wstringop-overflow was introduced it only detected
overflow in calls to C functions like strcpy or memcpy that aren't normally
seen in FORTRAN programs. It provided a means of
