This is the mail archive of the gcc-patches@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: [PATCH] use gcc_checking_assert instead of ENABLE_CHECKING/gcc_assert

From: Paolo Bonzini <bonzini at gnu dot org>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Nathan Froyd <froydnj at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
Date: Thu, 21 Oct 2010 17:59:57 +0200
Subject: Re: [PATCH] use gcc_checking_assert instead of ENABLE_CHECKING/gcc_assert
References: <20101021114100.GE2806@nightcrawler> <AANLkTi=8fOOh8D6CWeacdFD+Q+pO46x_S2i_ZRv9zoRD@mail.gmail.com>

On 10/21/2010 01:45 PM, Richard Guenther wrote:

I think that #ifdefed loops are more easy to identify as enabled
only in checkin mode.  And I'd be not so sure that the iterators
themselves are optimized if the loop is empty (they have calls
to non-inline fns at least).

Pointer chasing (e.g. on NEXT_INSN) is also not optimized, since it may trap.

Paolo

References:
- [PATCH] use gcc_checking_assert instead of ENABLE_CHECKING/gcc_assert
  - From: Nathan Froyd
- Re: [PATCH] use gcc_checking_assert instead of ENABLE_CHECKING/gcc_assert
  - From: Richard Guenther

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