HP/Alsys libmgr issue

HP/Alsys libmgr issue

[Jeff Dalton]

I'm currently using the HP Ada compiler (Alsys++) and I'm
attempting to "port" a development environment which we used
for both VAX/Ada and Verdix.  It consisted of three library 
levels (Alpha, Beta, Release) with unit search paths as follows:

Alpha   => Alpha, Beta, Release, Ada-Standard
Beta    => Beta, Release, Ada-Standard
Release => Release, Ada-Standard

Each library level contains multiple "objects" (A,B,C,...), but 
the architecture is flat within a level.  So if each object
was a library, then the search paths of a level would be as 
follows:

A => A, B, C ...       Each library would have unique units.      
B => B, A, C ...       So any given unit would only be found
C => C, B, A ...       in one of the libraries on each level.

With VADS and VAX/Ada we never had a problem with library size
so each level was one ada library and it would contain upwards
of 2000 units (4800 for Grace).  Our experience with the HP compiler 
is that the performance of the library manager gets so bad 
after 300-400 units are in the library (lots of thrashing I 
suppose), that it screems to be broken down further.

I'd like to know how any of you have broken down the Ada
development environment using the Alsys or HP Ada compiler on a
project which contained more than 5k unique units.


-- 
Jeff Dalton, ESL Inc.                    Real programmers can write 
jsd@esl.com                                 Fortran in any language.