Re: [PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-12-06 Thread Martin Sebor
On 12/6/19 8:44 AM, Christophe Lyon wrote: On Thu, 5 Dec 2019 at 02:37, Martin Sebor wrote: On 12/2/19 10:06 AM, Jeff Law wrote: On 11/8/19 3:11 PM, Martin Sebor wrote: Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow doesn't consider out-of-bounds accesses to objects allocated by

Re: [PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-12-06 Thread Christophe Lyon
On Thu, 5 Dec 2019 at 02:37, Martin Sebor wrote: > > On 12/2/19 10:06 AM, Jeff Law wrote: > > On 11/8/19 3:11 PM, Martin Sebor wrote: > >> Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow > >> doesn't consider out-of-bounds accesses to objects allocated > >> by alloca, malloc, other func

Re: [PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-12-04 Thread Martin Sebor
On 12/2/19 10:06 AM, Jeff Law wrote: On 11/8/19 3:11 PM, Martin Sebor wrote: Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow doesn't consider out-of-bounds accesses to objects allocated by alloca, malloc, other functions declared with attribute alloc_size, or even VLAs with variable b

Re: [PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-12-02 Thread Jeff Law
On 11/8/19 3:11 PM, Martin Sebor wrote: > Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow > doesn't consider out-of-bounds accesses to objects allocated > by alloca, malloc, other functions declared with attribute > alloc_size, or even VLAs with variable bounds.  This was > a known limit

[PING 2][PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-11-25 Thread Martin Sebor
Ping: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00652.html This change is independent of either of the two patches below: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00429.html https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00652.html On 11/18/19 11:22 AM, Martin Sebor wrote: Ping: htt

[PING][PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-11-18 Thread Martin Sebor
Ping: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00652.html On 11/8/19 3:11 PM, Martin Sebor wrote: Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow doesn't consider out-of-bounds accesses to objects allocated by alloca, malloc, other functions declared with attribute alloc_size, or

[PATCH] extend -Wstringop-overflow to allocated objects (PR 91582)

2019-11-08 Thread Martin Sebor
Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow doesn't consider out-of-bounds accesses to objects allocated by alloca, malloc, other functions declared with attribute alloc_size, or even VLAs with variable bounds. This was a known limitation of the checks (done just before expansion)