Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023]

On Fri, Feb 14, 2025 at 09:14:48AM -0500, David Malcolm wrote: > I haven't used ranger yet within the analyzer, and I wonder if there is > a philosophical divide here between the goals of optimization versus > bug finding: the optimizer makes use of undefined behavior in order to > add assumptions

Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023]

On Thu, 2024-11-14 at 11:19 +0100, Jakub Jelinek wrote: > Hi! Hi; sorry for the delay in responding to this. > > On top of the > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668554.html > patch which introduces the nonnull_if_nonzero attribute (because > C2Y is allowing NULL arguments

Patch ping^6 (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

On Thu, Feb 06, 2025 at 04:30:47PM +0100, Jakub Jelinek wrote: > On Tue, Jan 21, 2025 at 04:59:16PM +0100, Jakub Jelinek wrote: > > On Tue, Jan 07, 2025 at 01:49:04PM +0100, Jakub Jelinek wrote: > > > On Wed, Dec 18, 2024 at 12:15:15PM +0100, Jakub Jelinek wrote: > > > > On Fri, Dec 06, 2024 at 05:

Patch ping^5 (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

On Tue, Jan 21, 2025 at 04:59:16PM +0100, Jakub Jelinek wrote: > On Tue, Jan 07, 2025 at 01:49:04PM +0100, Jakub Jelinek wrote: > > On Wed, Dec 18, 2024 at 12:15:15PM +0100, Jakub Jelinek wrote: > > > On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote: > > > > I'd like to ping the > > >

Patch ping^4 (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

On Tue, Jan 07, 2025 at 01:49:04PM +0100, Jakub Jelinek wrote: > On Wed, Dec 18, 2024 at 12:15:15PM +0100, Jakub Jelinek wrote: > > On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote: > > > I'd like to ping the > > > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html > >

Patch ping^3 (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

On Wed, Dec 18, 2024 at 12:15:15PM +0100, Jakub Jelinek wrote: > On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote: > > I'd like to ping the > > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html > > patch. > > > > The patches it depended on are already committed and t

Patch ping^2 (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

Hi! On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote: > I'd like to ping the > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html > patch. > > The patches it depended on are already committed and there is a patch > which depends on this (the builtins shift from nonnu

Patch ping (Re: [PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023])

Hi! I'd like to ping the https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html patch. The patches it depended on are already committed and there is a patch which depends on this (the builtins shift from nonnull to nonnull_if_nonzero where needed) which has been approved but can't be

[PATCH] analyzer: Handle nonnull_if_nonzero attribute [PR117023]

Hi! On top of the https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668554.html patch which introduces the nonnull_if_nonzero attribute (because C2Y is allowing NULL arguments on various calls like memcpy, memset, strncpy etc. as long as the count is 0) the following patch adds just limited