Date: Sat, 1 Jul 2006 18:24:18 +0530 From: "Joseph Koshy" <joseph.koshy@gmail.com> To: "Dan Nelson" <dnelson@allantgroup.com> Cc: freebsd-hackers@freebsd.org, Jean-Marc Lienher <jml@oksidizer.com> Subject: Re: Alternative compiler toolchain ? Message-ID: <84dead720607010554w3ecc8618xb8ede50ac3fba29d@mail.gmail.com> In-Reply-To: <20060701032139.GB4915@dan.emsphone.com> References: <000f01c69ca5$02fa8ff0$6400a8c0@s2003> <20060701032139.GB4915@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
jml> I've found some other compilers on the web: jml> http://fabrice.bellard.free.fr/tcc/ (LGPL) dn> tcc is very fast, probably has the most modern C parser of dn> the lot, and might even be able to build world except that dn> the shared binaries it generates aren't able to be loaded dn> by our rtld. It looks like tcc only emits the bare dn> minimum to get Linux to run the executable, and I don't dn> know enough about the ELF format to fill in the blanks. Other bugs with tcc on FreeBSD: - tcc generated executables are missing an entry in their ELF program-header table and so do not execute directly. You can work around this by using the base system ld for the final link step. - Someone reported that a few of our headers don't compile with tcc. I haven't tracked down whether this is on account of an unsupported Gcc'ism in the header or whether this is a bug in tcc. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84dead720607010554w3ecc8618xb8ede50ac3fba29d>