Go to the first, previous, next, last section, table of contents.
A LIBPA module named module is implemented in the following files:
- `module.h'
-
public prototypes and typedefs for module
- `module.c'
-
source code for module
- `module.test.c'
-
source code for module test suite
- `module.test'
-
safe executable for module test suite
- `module.test_u'
-
unsafe executable for module test suite
- `Makefile'
-
Makefile for module
- `license'
-
Copyright notice, license, and disclaimer
The implementation may include other files, named according to a
similar naming convention, such as:
- `module.bench.c'
-
source code for module comparative benchmark
- `module.bench'
-
executable for module comparative benchmark
- `module.bench'
-
executable for module comparative benchmark (safe)
- `module.bench_u'
-
executable for module comparative benchmark (unsafe)
- `module.pure'
-
purified test suite for module (safe)
- `module.pure_u'
-
purified test suite for module (unsafe)
Special module functions may be provided a separate interface. For
example, the memory_t
library includes a `memory.spartan.h'
header file for the special-purpose spartan memory_t
functions.
As explained below, the object code for module is placed in an
archive named libmodule.a in the `libpa-1.3.0/lib.ARCH'
directory.
Go to the first, previous, next, last section, table of contents.