[Bug middle-end/85650] Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650 Martin Sebor changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org --- Comment #3 from Martin Sebor --- I'll work on this for GCC 9.
[Bug middle-end/85650] Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2018-05-08 CC||msebor at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Martin Sebor --- I actually view the warning in attachment 44067 as a feature (though one that just coincidentally happens to be enabled by the UBSan instrumentation) and its absence as a feature request. The warning in attachment 44068 is the opposite: the UBSan instrumentation gets in the way of the warning seeing the assignment as a suppression mechanism. The instrumentation in this case is pointless and can be removed with no loss of efficacy -- see bug 79265.
[Bug middle-end/85650] Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650 --- Comment #1 from Franz Sirl --- Created attachment 44068 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44068=edit testcase 2
