This shows you the differences between two versions of the page.
tutorials:kcc [2014/01/28 07:05] papa created |
tutorials:kcc [2014/06/09 06:48] (current) vulcan |
||
---|---|---|---|
Line 7: | Line 7: | ||
- **K&R C**. KCC supports only the " | - **K&R C**. KCC supports only the " | ||
- **Missing libraries**. KCC does not include all of the standard C libraries. //(List missing libraries)// | - **Missing libraries**. KCC does not include all of the standard C libraries. //(List missing libraries)// | ||
- | - **Executable bloat**. KCC was written with the goal of porting BSD programs to the PDP-10. Therefore, although KCC generates relocatable object files of size comparable to the TOPS-20 native MACRO assembler and FORTRAN compiler, the loader links in a large BSD compatibility layer object module and produces executable files much larger than those of other programming languages. //(Are there compiler or loader options that can prevent linking of the BSD compatibility layer module?)// | + | - **Executable bloat**. KCC was written with the goal of porting BSD programs to the PDP-10. Therefore, although KCC generates relocatable object files of size comparable to the TOPS-20 native MACRO assembler and FORTRAN compiler, the loader links in a large BSD compatibility layer object module and produces executable files much larger than those of other programming languages. //(Are there compiler or loader options that can prevent linking of the BSD compatibility layer module? |
- | - **Absent Unix utilities**. | + | - **Absent Unix utilities**. |
Therefore KCC is probably best used on projects porting software from a BSD environment and/or projects where the target executable file is expected to be relatively large. | Therefore KCC is probably best used on projects porting software from a BSD environment and/or projects where the target executable file is expected to be relatively large. | ||