This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: telling GCC that a pointer cannot be NULL

From: Igor Bukanov <igor at mir2 dot org>
To: gcc-help at gcc dot gnu dot org
Date: Tue, 10 May 2011 19:53:27 +0200
Subject: Re: telling GCC that a pointer cannot be NULL
References: <BANLkTimU35Ss1Rfc8CG0=AKur9zzj2C+_A@mail.gmail.com> <alpine.DEB.2.02.1105101350150.13417@stedding.saclay.inria.fr>

On 10 May 2011 13:51, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Tue, 10 May 2011, Igor Bukanov wrote:
>
>> is it possible to tell GCC that a pointer cannot be NULL at a
>> particular point so the compiler can optimize the control flaw better
>> and avoid redundant NULL checks on the fast paths?
>
> I seem to remember that dereferencing the pointer had that effect.

Yes, this is indeed the case in the cases I checked. So I would need
to refactor much less code, thanks!

References:
- telling GCC that a pointer cannot be NULL
  - From: Igor Bukanov
- Re: telling GCC that a pointer cannot be NULL
  - From: Marc Glisse

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]