From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,6c43f45c2ab47c51
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news.glorb.com!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: Using Ada.Containers.Vector and Limited Private types
Date: Wed, 16 Jul 2008 22:23:18 +0100
Organization: Pushface
Message-ID: <m2mykhed6h.fsf@mac.com>
References: <MrNoSpam-843547.21533805072008@news-server.bigpond.net.au>
 <8ff4c6c2-9892-463e-bdfd-1f7bfd78d607@s50g2000hsb.googlegroups.com>
 <MrNoSpam-A95CF0.10160610072008@news-server.bigpond.net.au>
 <4c5bfeb0-daa0-45e4-82f0-eebabda565e9@d45g2000hsc.googlegroups.com>
 <6QQdk.194211$TT4.37376@attbi_s22>
 <940db060-ef08-4e1c-9556-0514181183eb@j22g2000hsf.googlegroups.com>
 <%BWdk.194588$TT4.100135@attbi_s22>
 <16cdae3f-83fa-4bd2-a9d1-3750518ff9d8@y38g2000hsy.googlegroups.com>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1216243398 11366 62.49.19.209 (16 Jul 2008 21:23:18
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Wed, 16 Jul 2008 21:23:18 +0000 (UTC)
Cancel-Lock: sha1:x7xa8mWpzZ+MWOB50rJ2FV/dXhI=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (darwin)
Xref: g2news1.google.com comp.lang.ada:1179
Date: 2008-07-16T22:23:18+01:00
List-Id: <comp.lang.ada>

Gene <gene.ressler@gmail.com> writes:

> You might want to be careful about this. I guess it depends how soft
> soft is. Internally it looks like GNAT ends up calling gcc
> malloc/free for UBS.  Implementations of malloc/free can have wildly
> varying performance depending on current heap structure.  Your app
> may meet time requirements today on test data and fail tomorrow
> because the heap has fragmented in a different way.

I can support this! malloc/free in VxWorks 5.5, for example, can
behave very badly if you have even a small leak amidst a lot of memory
churn.