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.5 required=5.0 tests=BAYES_00,
	PP_MIME_FAKE_ASCII_TEXT,REPLYTO_WITHOUT_TO_CC,XPRIO autolearn=no
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,3d251c18d8b3155d,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-11-26 00:40:35 PST
Path: 
 archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!gate.dornier.dasa.DE!not-for-mail
From: "Joachim Schr�er" <joachim.schroeer@dornier.eads.net>
Newsgroups: comp.lang.ada
Subject: High compilation time with gnat
Date: Wed, 26 Nov 2003 09:40:19 +0100
Message-ID: <bq1ou1$1tcm0d$1@ID-76083.news.uni-berlin.de>
Reply-To: "Joachim Schr�er" <joachim.schroeer@dornier.eads.net>
NNTP-Posting-Host: gate.dornier.dasa.de (53.122.46.165)
X-Trace: news.uni-berlin.de 1069836034 64378893 53.122.46.165 ([76083])
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Xref: archiver1.google.com comp.lang.ada:2952
Date: 2003-11-26T09:40:19+01:00
List-Id: <comp.lang.ada>

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