From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 required=3.0 tests=BAYES_00,NICE_REPLY_A
	autolearn=ham autolearn_force=no version=3.4.6
Path: eternal-september.org!reader02.eternal-september.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Custom Storage Pool questions
Date: Mon, 20 Sep 2021 09:34:47 +0300
Organization: Tidorum Ltd
Message-ID: <iqqoc7F2lr8U1@mid.individual.net>
References: <e3c5c553-4a7f-408a-aaa7-60ec0b70202dn@googlegroups.com>
 <shmnk1$lgf$1@franka.jacob-sparre.dk>
 <9bc55d72-b90e-45c5-bfd8-cbce565d139dn@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net V1vgHVyuix+v1KKiaWZ80gWyheVjD5I/FfCEt++8PSuZ+RLJM+
Cancel-Lock: sha1:+JpkGMahxK3Pms9IEyRELm/e6Gc=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0)
 Gecko/20100101 Thunderbird/78.13.0
In-Reply-To: <9bc55d72-b90e-45c5-bfd8-cbce565d139dn@googlegroups.com>
Content-Language: en-US
Xref: reader02.eternal-september.org comp.lang.ada:62781
List-Id: <comp.lang.ada>

On 2021-09-20 3:31, Jere wrote:
> Followup question cause Randy's statement (below) got me thinking:
> If a compiler is allowed to break up an allocation into multiple
> calls to Allocate (and of course Deallocate), how does one go about
> enforcing that the user's header is only created once?


I think one cannot enforce that, because the calls to Allocate do not 
indicate (with parameters) which set of calls concern the same object 
allocation.

This is probably why Dmitry said that such compiler behaviour would 
"disqualify the compiler" for his uses.