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
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!newsfeed.kamp.net!newsfeed.kamp.net!newsfeed.fsmpi.rwth-aachen.de!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Wed, 13 Nov 2013 12:04:12 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Increasing GNAT's heap
References: <1o29hesl8k6yk$.1kqputng2vdks$.dlg@40tude.net>
 <87habgiufi.fsf@ludovic-brenta.org>
 <1ogylkzganxtj.1fuy036v94ui4$.dlg@40tude.net>
In-Reply-To: <1ogylkzganxtj.1fuy036v94ui4$.dlg@40tude.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <52835cab$0$9515$9b4e6d93@newsspool1.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 13 Nov 2013 12:04:11 CET
NNTP-Posting-Host: c59a39e9.newsspool1.arcor-online.net
X-Trace: 
 DXC=7lCTh:3cKBd^Y=RbYBPl4`ic==]BZ:afn4Fo<]lROoRankgeX?EC@@`?Z7BlCkWK7gPCY\c7>ejVhM4DQXZ<G35f:X5a\R814Zd
X-Complaints-To: usenet-abuse@arcor.de
Xref: news.eternal-september.org comp.lang.ada:17649
Date: 2013-11-13T12:04:11+01:00
List-Id: <comp.lang.ada>

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. Gcc hits the ceiling
(or floor) for even a short C program:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56344

Another way to ask, then, might be, if there is a GNAT
executable that will itself use a PAE kernel's extended addressing?

If doubling memory only defers the issue, maybe that's something
to ask on the GCC list?