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: border1.nntp.ams.giganews.com!nntp.giganews.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Oliver Kleinke Newsgroups: comp.lang.ada Subject: Re: Increasing GNAT's heap Date: Wed, 13 Nov 2013 19:44:21 +0100 Organization: A noiseless patient Spider Message-ID: <20131113194421.20f75f6b@PC-8N-L> References: <1o29hesl8k6yk$.1kqputng2vdks$.dlg@40tude.net> <87habgiufi.fsf@ludovic-brenta.org> <1ogylkzganxtj.1fuy036v94ui4$.dlg@40tude.net> <20131113163213.5c4df4e2@PC-8N-L> <1na6et9vn387k.1klqijlk4ai6e.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: mx05.eternal-september.org; posting-host="434901b96fa29c45bb85d71213c80cc9"; logging-data="24142"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/XxNzi/EMzBKUMJijsXKln4zBU7TzjcMs=" X-Newsreader: Claws Mail 3.9.2 (GTK+ 2.24.21; x86_64-pc-linux-gnu) Cancel-Lock: sha1:doT8joV+3fhpDMq0ETI9VRcORXE= Xref: number.nntp.dca.giganews.com comp.lang.ada:183866 Date: 2013-11-13T19:44:21+01:00 List-Id: Am Wed, 13 Nov 2013 18:36:38 +0100 schrieb "Dmitry A. Kazakov" : > On Wed, 13 Nov 2013 16:32:13 +0100, Oliver Kleinke wrote: > > > Various chunks of the 32-bit address space are used to address > > various hardware devices in your machine, e.g. PCI devices, APIC > > etc. IIRC, how much address space is "wasted" depends on the > > hardware. So in essence you will never get 4GiB of RAM on a 32-bit > > machine. > > The question is whether that is closer to 4 or to 2. Under Windows it > is strictly 2. If Linux reserves lesser chunks of the address space > then it should be able to compile the program which at its peak takes > 2.6GB for gnat1 under Windows. However, lesser chunks would mean more > of them and thus more overhead for handling the process address space. Should be in the range of 3 - 3.5 GiB, though it depends on your hardware (try free or cat /proc/meminfo).