Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: BartC Newsgroups: comp.compilers Subject: Re: Alternative C compilers on x86_64 Linux? Date: Mon, 12 Sep 2016 22:37:12 +0100 Organization: A noiseless patient Spider Lines: 15 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <16-09-028@comp.compilers> References: <16-09-001@comp.compilers> <16-09-026@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="39893"; mail-complaints-to="abuse@iecc.com" Keywords: C Posted-Date: 13 Sep 2016 10:49:07 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1767 On 12/09/2016 19:42, Aharon Robbins wrote: > Privately by someone else, I was suggested to just fix tcc myself. > It turns out that I was able to add duplicate case checking in about > an hour's work and just under 100 lines of code. But I have the > background and experience for that; I suspect someone else would > have had a harder time. Do you use TCC to compile itself, or something like gcc? I'm just interested in whether it partly relies on gcc to get its speed! -- Bartc