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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Increasing GNAT's heap
Date: Wed, 13 Nov 2013 14:31:07 +0100
Organization: cbb software GmbH
Message-ID: <1gyri4u994iza.15tpx0vnp77zr.dlg@40tude.net>
References: <1o29hesl8k6yk$.1kqputng2vdks$.dlg@40tude.net>
 <87habgiufi.fsf@ludovic-brenta.org>
 <1ogylkzganxtj.1fuy036v94ui4$.dlg@40tude.net>
 <52835cab$0$9515$9b4e6d93@newsspool1.arcor-online.net>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: IenaDxMXK2hi7fvYcb+MlQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
X-Original-Bytes: 2110
Xref: number.nntp.dca.giganews.com comp.lang.ada:183854
Date: 2013-11-13T14:31:07+01:00
List-Id: <comp.lang.ada>

On Wed, 13 Nov 2013 12:04:12 +0100, Georg Bauhaus wrote:

> On 13.11.13 09:58, Dmitry A. Kazakov wrote:
>> On Wed, 13 Nov 2013 09:21:05 +0100, Ludovic Brenta wrote:
>>
>>> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
>>>> Does anybody know a way to increase the heap size available for GNAT? It
>>>> crashes with famous GNAT BUG DETECTED, Storage_Error heap exhausted.
>>>>
>>>> GNAT 4.6.4 under Debian, testing, 32-bit
> 
>> The compiler starts
>> frantically allocating huge amounts of memory, expanding generics, I
>> suppose. This is how it comes to gigabytes when compiling a mere 100-liner.
> 
> Ouch, I had completely misread the question.  Voracious consumption
> of memory is also a property of GCC for C.

I don't believe it has anything to do with GCC. It looks clearly like GNAT
issue which, BTW, also leads to extremely sluggish compilation. After all,
if you allocate 2+ GB of memory you have to fill it with some junk and that
takes time, much time.

If AdaCore didn't fix it, that is probably because, I guess, it would
require to redesign much of the compiler code.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de