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!mx02.eternal-september.org!feeder.eternal-september.org!newsfeed0.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Too big
Date: Thu, 24 Mar 2016 07:50:01 +0200
Organization: Tidorum Ltd
Message-ID: <dlhdgaF52a9U1@mid.individual.net>
References: <eb06b468-3a3c-4272-84d9-3a1dcc4a59df@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net PJaAGhks5NeD8Z5cWYKt4QQXBwZbAQHXA0vXcKyrbIrE8sWOuU
Cancel-Lock: sha1:69MRoSKUOHfJuXbrjRG9w7DDubE=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:38.0)
 Gecko/20100101 Thunderbird/38.7.0
In-Reply-To: <eb06b468-3a3c-4272-84d9-3a1dcc4a59df@googlegroups.com>
Xref: news.eternal-september.org comp.lang.ada:29872
Date: 2016-03-24T07:50:01+02:00
List-Id: <comp.lang.ada>

On 16-03-24 00:18 , mike-h@ada-augusta.demon.co.uk wrote:
> "gnatmake -ws -c -u -PC:\Users\Mike\Desktop\Ada\Sudoku_solver\solver.gpr solver-solve.adb
> gcc -c -I- -gnatA C:\Users\Mike\Desktop\Ada\Sudoku_solver\solver-solve.adb
> cannot generate code for file solver-solve.adb (subunit)
> gnatmake: "C:\Users\Mike\Desktop\Ada\Sudoku_solver\solver-solve.adb" compilation error
> [2016-03-23 21:55:41] process exited with status 4 (elapsed time: 03.37s)"
>
> What is the most likely reason? For example, the offending subunit
> contains a large number of "separate" procedures. Would it help to
> wrap them up in a package?

GNAT's message suggests to me that solver-solve.adb is itself a subunit 
(of solver). GNAT cannot fully compile subunits separately; it can check 
their syntax and semantics, but cannot generate code. GNAT generates the 
code for subunits when it compiles the parent unit. So for GNAT, "is 
separate" works somewhat as "#include" in C.

For example, if I have, in solver.adb:

procedure Solver
is
    X : Integer;

    procedure Solve (A : in out Integer)
    is separate;

begin
    X := 14;
    Solve (X);
end Solver;

and then in solver-solve.adb:

separate (Solver)
procedure Solve (A : in out Integer)
is begin
   A := A + 1;
end Solve;

and give the command "gnatmake -ws -c -u solver-solve.adb" I get

gcc -c solver-solve.adb
cannot generate code for file solver-solve.adb (subunit)
gnatmake: "solver-solve.adb" compilation error

but the command "gnatmake -ws -c -u solver.adb" succeeds and creates 
solver.o.

A consequence of this GNAT property is that dividing a large unit into 
subunits decrease source-file size, but does not decrease compile-time.

Can your problem be this simple?

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .