https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68201
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68201
--- Comment #2 from Daniel Fruzynski ---
What about code compiled with -D_FORTIFY_SOURCE=1, when functions like strcpy
are replaced with __builtin___strcpy_chk? This is a runtime check, so passing
pool->block_size should be reasonable there.
Inl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68201
--- Comment #1 from Richard Biener ---
As GCC uses the attribute for static analysis it can't go out and read the
actual
value from pool->block_size so I see no value in providing the size this way
(it would also only work if pool_alloc is inline
