Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Jan 2012 21:14:35 +0100
From:      Roland Smith <>
Subject:   Re: Clang - what is the story?
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <20120122070205.GA13081@hemlock.hydra> <> <20120122074558.GA22918@hemlock.hydra> <> <20120122123748.GA26579@hemlock.hydra> <> <20120122212653.GA2489@hemlock.hydra> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 23, 2012 at 08:53:36AM +1000, Da Rock wrote:
> On 01/23/12 07:26, Chad Perrin wrote:
> > On Sun, Jan 22, 2012 at 09:33:02PM +0100, Roland Smith wrote:
> >> PCC is only a C compiler, and there is some C++ code (e.g. groff) in t=
he base
> >> system. The FreeBSD port is marked as i386 and amd64 only, even though=
> >> architectures seem to be there in the PCC source.
> > I had somehow forgotten there was anything in the base system written in
> > C++.  That would probably account for the choice of Clang over PCC.
> What part is that? I thought it had to be all c...

To the best of my knowledge the restriction to C only applies to the kernel
and libraries, not to the utilities in the base system. And it is for a
technical reason. C++ "mangles" function names to e.g. include argument typ=
and class names. See=20
This practically means that you can use a C library from a C++ program, but=
the other way around.

Then again, the kernel has more restrictions. Like no floating point allowed
and no libc available. And presumably many more w.r.t. locking of data
structures and practical limits on interrupt handlers.

[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

Content-Type: application/pgp-signature

Version: GnuPG v2.0.18 (FreeBSD)



Want to link to this message? Use this URL: <>