On 04/26/2012 08:57 AM, Eric Blake wrote:
On 04/26/2012 12:56 AM, Laine Stump wrote:
The ATTRIBUTE_NONNULL(m) macro normally resolves to the gcc builtin
__attribute__((__nonnull__(m))). The effect of this in gcc is
unfortunately only to make gcc believe that m can never possibly be
NULL,
The ATTRIBUTE_NONNULL(m) macro normally resolves to the gcc builtin
__attribute__((__nonnull__(m))). The effect of this in gcc is
unfortunately only to make gcc believe that m can never possibly be
NULL, *not* to add in any checks to guarantee that it isn't ever NULL
(i.e. it is an optimization
On 04/26/2012 12:56 AM, Laine Stump wrote:
The ATTRIBUTE_NONNULL(m) macro normally resolves to the gcc builtin
__attribute__((__nonnull__(m))). The effect of this in gcc is
unfortunately only to make gcc believe that m can never possibly be
NULL, *not* to add in any checks to guarantee that it