|Original author(s)||Stephen C. Johnson|
|Developer(s)||AT&T Bell Laboratories|
1.1.0 / December 10, 2014
|Operating system||Unix and Unix-like|
The Portable C Compiler (also known as pcc or sometimes pccm - portable C compiler machine) is an early compiler for the C programming language written by Stephen C. Johnson of Bell Labs in the mid-1970s, based in part on ideas proposed by Alan Snyder in 1973, and "distributed as the C compiler by Bell Labs... with the blessing of Dennis Ritchie."
One of the first compilers that could easily be adapted to output code for different computer architectures, the compiler had a long life span. It debuted in Seventh Edition Unix and shipped with BSD Unix until the release of 4.4BSD in 1994, when it was replaced by the GNU C Compiler. It was very influential in its day, so much so that at the beginning of the 1980s, the majority of C compilers were based on it. Anders Magnusson and Peter A Jonsson restarted development of pcc in 2007, rewriting it extensively to support the C99 standard.
The keys to the success[according to whom?] of pcc were its portability and improved diagnostic capabilities. The compiler was designed so that only a few of its source files were machine-dependent. It was relatively robust to syntax errors and performed more thorough validity checks than its contemporaries.[according to whom?]
The first C compiler, written by Dennis Ritchie, used a recursive descent parser, incorporated specific knowledge about the PDP-11, and relied on an optional machine-specific optimizer to improve the assembly language code it generated. In contrast, Johnson's pccm was based on a yacc-generated parser and used a more general target machine model. Both compilers produced target-specific assembly language code which they then assembled to produce linkable object modules.
Later versions of PCC, known within Bell Labs as "QCC" and "RCC," supported other target architecture models.
The language that PCC implemented was an extended version of K&R C that Bjarne Stroustrup has called "Classic C", incorporating the
void return type (for functions that don't return any value), enumerations and structure assignment.
A new version of pcc, based on the original by Steve Johnson, is now maintained by Anders Magnusson. The compiler is provided under the BSD licence and its development is funded by a non-profit organization called BSD Fund. According to Magnusson:
The big benefit of it (apart from that it's BSD licensed, for license geeks) is that it is fast, 5-10 times faster than gcc, while still producing reasonable code. <...> [I]t is also quite simple to port...— Anders Magnusson
This new version was added to the NetBSD pkgsrc and OpenBSD source trees in September 2007, and later into the main NetBSD source tree. There had been some speculation that it might eventually be used to supplant the GNU C Compiler on BSD-based operating systems, though FreeBSD and NetBSD are both looking to Clang as a potential replacement, and Theo de Raadt of OpenBSD asserts that pcc is not ready yet to be a gcc replacement, and the disposal of gcc is not top priority. On December 29, 2009 pcc became capable of building a functional x86 OpenBSD kernel image.
pcc version 1.0 was released on 1 April 2011. As of this release, the compiler supports x86 and x64 processor architectures and runs on NetBSD, OpenBSD, FreeBSD, various Linux distributions, and Microsoft Windows. Further development, including support for more architectures, and FORTRAN 77 and C++ front ends, is continuing.
PCC was removed from the OpenBSD source tree in 2012. Development on it had stalled and no maintainer had stepped up to develop it into something that could make a practical alternative to GNU Compiler Collection.
The latest version of pcc, namely 1.1.0, was released on 10 December 2014.
At the start of the decade, nearly every compiler was based on Johnson's pcc; by 1985 there were many independently-produced compiler products.
But that’s never really been the agenda, see. Some people think we hate GNU code. But the thing is we hate large code, and buggy code that upstream does not maintain. That’s the real problem… gcc gets about 5-6% slower every release, has new bugs, generates crappy code, and drives us nuts. This is just an attempt to see if something better can show up.
Edited: 2021-06-18 15:15:06