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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,3d251c18d8b3155d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-28 00:12:15 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: volkert@nivoba.de (Volkert) Newsgroups: comp.lang.ada Subject: Re: High compilation time with gnat Date: 28 Nov 2003 00:11:47 -0800 Organization: http://groups.google.com Message-ID: References: NNTP-Posting-Host: 138.189.120.38 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1070007135 25588 127.0.0.1 (28 Nov 2003 08:12:15 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 28 Nov 2003 08:12:15 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:3013 Date: 2003-11-28T00:11:47-08:00 List-Id: "Joachim Schr�er" wrote in message news:... > Hello, > we have a package spec which uses an enormous compilation time. One of the > specs it withes has about 40_000 lines of source. When I remember correctly > the gnat parser parses all specs in the closure of a given compuation unit. > This sum has a size of about 60_000 loc. > The compilation time seems to rise very nonlinear with the size of single > compilation units. The system is mainly paging to and from harddisc. > Is there a compilation switch for gnat to increase the amount of main memory > it uses or is there any other measure one may take? > Rewriting the source is no option, cause it is a delivery. > > Thanks for any help > Joachim Schr�er You haven`t a service contract with ACT ???? I would ask them ... Volkert