Re: Using local storage pools...

[Brian Drummond <brian_drummond@btconnect.com>]

On Wed, 23 Feb 2011 21:51:20 +0100, Ludovic Brenta <ludovic@ludovic-brenta.org>
wrote:

>Brian Drummond writes:
>> I am trying to learn a little about storage pools, with a view to
>> (hopefully) using local pools to improve the Binary_Trees benchmark in
>> the same way as some of the faster C benchmarks.

>> ------------------------------------------------------------------------------------
>
>This looks like a genuine bug at s-pooloc.adb:114.  To trigger the bug,
>two conditions must hold simultaneously:
>
>* the pool contains exactly one allocated object.
>* the user calls Unchecked_Deallocation on this object.

Good detective work, thanks.

>Because this pool is intended for use without any explicit
>Unchecked_Deallocation, I would qualify this bug as minor.

I believe it should support both strategies (especially since it HAS a
"deallocate")  but I can't argue it's anything other than minor if I'm the first
to find it!

>The workaround, in your case, is to simply not do any
>Unchecked_Deallocation and let the finalization of the storage pool do
>the deallocation.

Which was the original intent.

Thanks for the detective work!

I have been emailed privately, suggesting I report it to Adacore.
Should I also report it to either Debian, or mainstream GCC?

- Brian