This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 5/9] ENABLE_CHECKING refactoring: pool allocators
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Bernd Schmidt <bschmidt at redhat dot com>
- Cc: Mikhail Maltsev <maltsevm at gmail dot com>, gcc-patches mailing list <gcc-patches at gcc dot gnu dot org>, Jeff Law <law at redhat dot com>
- Date: Tue, 6 Oct 2015 14:45:13 +0200
- Subject: Re: [PATCH 5/9] ENABLE_CHECKING refactoring: pool allocators
- Authentication-results: sourceware.org; auth=none
- References: <56130763 dot 4070206 at gmail dot com> <5613088F dot 9010903 at gmail dot com> <5613C17C dot 5090703 at redhat dot com>
On Tue, Oct 6, 2015 at 2:41 PM, Bernd Schmidt <bschmidt@redhat.com> wrote:
> On 10/06/2015 01:32 AM, Mikhail Maltsev wrote:
>>
>> gcc/ChangeLog:
>>
>> 2015-10-05 Mikhail Maltsev <maltsevm@gmail.com>
>>
>> * alloc-pool.h (base_pool_allocator::initialize, ::allocate,
>> ::remove): Adjust to use CHECKING_P.
>
>
> Why CHECKING_P for these and not flag_checking as elsewhere?
Probably because they are in inline functions and thus possibly would
affect optimization. Not sure why they are inline functions in the
first place... I'd agree to using flag_checking here.
Richard.
>
> Bernd