https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83106
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> --- Yes, exactly. It's these unintended uses that are a common problem and that the warning is designed to help prevent. They are rare in carefully written code bases like GCC but more common in software developed by less experienced programmers. Often they come up as code is being updated to comply with a security policy (e.g., replace all strcpy/strcat calls with "safe bounded functions"). The warning tries to avoid triggering for the safe uses where it can but there is, unfortunately, not always a good way to do that.
