Iron Spring PL/I Compiler

Introduction

  pli-0.9.2
    |
    +-----------------------samples----------------lib
    |                          |                    |
 plic                       (Sample sources and     +--------------------------static---include----source-----------alt
 (compiler executable)       %include files,                                   |         |         |                 | 
 (documentation, etc.)       sample makefiles                                  |         |         +--------asm      |
                             and module definition                             |         |   (PL/I source)   |     (alt storage   
                             file).                                            |         |               (assembler management)
                                                                               |  (%include files          source)
                                                                               |    required by                                                                                      
                                                                               |     library).
                                                                               |
                                                                     libprf.a (static library)

Requirements

Restrictions

• The compiler cannot yet generate position-independent code (PIC) required to build shared objects. As a result, only static linking to the PL/I library is available.

Installation

1. The distribution file is supplied as a gzipped tar file. Unpacking it will create a directory named "pli-0.9.2".
2. Only the compiler (pli-0.9.2/plic) and the static runtime library (pli-0.9.2/lib/libprf.a) are required.
3. Move the compiler to a directory in your $PATH such as /usr/bin, and move libprf.a to a directory such as /usr/lib. Alternatatively, you can specify which directory the library is in in your makefiles.
   An installation procedure is provided. cd to the 'pli-0.9.2' directory and type 'make install' (with suitable authority). This procedure moves the compiler to '/usr/bin' and creates a symlink 'plic' referencing it, and moves the library to '/usr/lib' and creates the symlink 'libprf.a'.
4. Test the sample programs. In this release only static linking is supported. CD to the directory "pli-0.9.2/samples" and type "make". The sample programs "numwrd", "filedump", "libver", "print_listing", and "task" build to executables, the remainder should generate object files.
5. Test numwrd. Enter "./numwrd 123". The program should display the result "one hundred twenty-three".
6. You might want access to the %INCLUDE files in "pli-0.9.2/lib/include" or "pli-0.9.2/samples" for your own programming.

• Compiled PL/I programs have no external dependencies. If no calls are made to functions coded in the C language the only library required is the PL/I runtime library 'libprf.a'. The sample makefile 'SA_make' compiles a PL/I program and links without referencing libc.
• If any C functions are called, the PL/I program should be linked with libc; the sample makefile 'LC_make' compiles a PL/I program and uses the Gnu C Compiler (gcc) to link it. It is possible to link with ld, but using gcc eliminates libc version dependencies.
• The PL/I library includes its own heap storage management. Programs linked with libc can use libc's heap management for both PL/I and C storage, or can use separate heaps for the PL/I and C portions. As distributed the library will use separate heaps. Versions of allocate and release are provided in the directory pli-0.9.2/lib/alt will use C's malloc and free. The sample makefile 'LCC_make' shows how to link these procedures.

This command uses gcc to link a PL/I program with libc, and use C's malloc and free for heap storage management.

gcc -o ${EXE} ${OBJ} ${ALTDIR}/fhs.o ${ALTDIR}/ghs.o -lprf -Wl,-M >${MAP}

• Replace ${EXE} with the name of your excecutable.
• Replace ${OBJ} with the name of your compiled object file (.o)
• Replace ${ALTDIR} with the name of the directory containing the alternate storage management modules. For example, the default is /pli-0.9.2/lib/alt
• Replace ${MAP} with the name of your link map (.map)

This command uses gcc to link a PL/I program with libc, and use PL/I's heap storage management.

gcc -o ${EXE} ${OBJ} -lprf -Wl,-M >${MAP}

• Replace ${EXE} with the name of your excecutable.
• Replace ${OBJ} with the name of your compiled object file (.o)
• Replace ${MAP} with the name of your link map (.map)

This command uses ld to link a standalone PL/I program with no reference to libc.

ld -z muldefs -Bstatic -M -e main -t -o ${EXE} \ ${OBJ} \ -lprf \ >${MAP}

• Replace ${EXE} with the name of your excecutable.
• Replace ${OBJ} with the name of your compiled object file (.o)
• Replace ${MAP} with the name of your link map (.map)

Modifying the Runtime Library