https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
--- Comment #8 from Martin Sebor ---
I would expect the additional detail (about the structure of data) to only help
improve things, not ever make them worse, or introduce bugs into correct code.
But relying on the structure of data is not novel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
--- Comment #7 from rguenther at suse dot de ---
On Mon, 25 Jun 2018, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
>
> --- Comment #6 from Martin Sebor ---
> The strlen range optimization doesn't take a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
--- Comment #6 from Martin Sebor ---
The strlen range optimization doesn't take advantage of undefined behavior --
like all other optimizations, it simply assumes code is free of it.
I have two goals for the warnings I work on: a) most important
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
--- Comment #5 from rguenther at suse dot de ---
On Thu, 21 Jun 2018, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
>
> --- Comment #4 from Martin Sebor ---
> Using strncpy or strlen to cross subobject b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
--- Comment #4 from Martin Sebor ---
Using strncpy or strlen to cross subobject boundaries isn't valid. GCC catches
the strncpy bug with -Warray-bounds:
pr86265.c: In function ‘main’:
...
In file included from /usr/include/string.h:630,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
Richard Biener changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
Richard Biener changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86265
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
