8. Summary of numerical characteristics

The table below gives the number of files in the UnixWare source delivery in respect to the programming language being used. Header files are not counted.

The following table applies to the DRA-NAT build; it gives the number of C source files and ratios of code compiled by TenDRA versus code compiled by the native compiler. We distinguish the two reasons for using the native C compiler: because of assembly language inclusions, or because of use of pragma pack directive.

Note that for libraries, the Netware protocols are responsible for the high number of C sources dependent on the pragma pack feature.

The following numbers characterize the maturity of the TenDRA C compilation chain and the level of UnixWare source code portability, as shown by the DRA-NAT phases of our project:

The table below shows the performance of the native system versus that of DRA-NAT kernel and libc library as measured by the AIMIII benchmark; the shared variant of libc is used.

While the DRA-DRA phase was only partially realized, it is interesting to note that 62 additional source files were so far modified to enforce the portability of code, e.g.to avoid implicit function declarations. The following tables give an idea of the volume of items which must be added to the base API to compile a limited set of commands in DRA-DRA mode.

By extension we mean the adding of a specification such as defining a function, a constant, a field inside a structure, etc.