[Bug tree-optimization/103835] bogus sprintf warnings due to missing strlen propagation

2022-01-06 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103835 --- Comment #5 from Martin Sebor --- It's the same cause. When the -Wformat-overflow and -truncation warnings are unable to compute the exact length of a string argument to a directive like %s they use the size of the array the string is stored

[Bug tree-optimization/103835] bogus sprintf warnings due to missing strlen propagation

2022-01-05 Thread lavr at ncbi dot nlm.nih.gov via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103835 --- Comment #4 from lavr at ncbi dot nlm.nih.gov --- Thank you for investigating this! Like I said, it's better NOT to emit any warnings if some machinery in the compiler is not perfect enough to recognize the danger correctly (as it used to be

[Bug tree-optimization/103835] bogus sprintf warnings due to missing strlen propagation

2022-01-04 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103835 Martin Sebor changed: What|Removed |Added Summary|Bogus sprintf warnings |bogus sprintf warnings due

[Bug tree-optimization/103835] Bogus sprintf warnings

2021-12-27 Thread lavr at ncbi dot nlm.nih.gov via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103835 --- Comment #2 from lavr at ncbi dot nlm.nih.gov --- Irrespective of whether atoi() is known, printing an "int" (or two) will never produce this many characters... This, however, also seems to have triggered some weird logic that took the entire

[Bug tree-optimization/103835] Bogus sprintf warnings

2021-12-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103835 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-12-26 Keywords|