A portable C compiler implementation with BSD license, originally developed for Unix systems.
Portable C Compiler (pcc) is an open-source C compiler implementation originally developed for Unix systems. It provides an alternative C compilation toolchain with emphasis on portability across different platforms. The project solves the need for a portable, BSD-licensed C compiler that can be adapted to various Unix-like environments.
System developers and compiler enthusiasts working with Unix-like systems who need a portable C compiler implementation. This includes maintainers of legacy systems and those interested in compiler internals.
Developers choose pcc for its historical significance in the Unix ecosystem, clean BSD licensing, and portable design that can be adapted to various platforms. It offers an alternative to mainstream compilers with simpler implementation.
Portable C Compiler sources
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designed from the original Unix C compiler tradition, pcc is built to run on multiple Unix platforms with minimal dependencies, as emphasized in the README's focus on portability.
The source is BSD licensed, providing permissive terms for adaptation and distribution, as stated in the COPYING file, which is a key value for open-source toolchains.
As a historical implementation, it offers a clean codebase for studying compiler design and Unix development practices, making it ideal for enthusiasts and learners.
Following the Unix philosophy, pcc emphasizes simplicity and minimalism, providing a straightforward compiler without excessive complexity, as noted in the project description.
This repository is a mirror from a 2018 CVS snapshot, and the owner explicitly states inability to fix issues, meaning no updates, bug fixes, or security patches.
Since it's not actively developed, pcc likely lacks modern C features, optimizations, and compatibility with newer systems, making it risky for current use.
The README only explains the source origin with no installation guides, user manuals, or API references, creating barriers for practical adoption.