Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Muttley@DastardlyHQ.org Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Tue, 18 Mar 2025 16:36:29 -0000 (UTC) Organization: A noiseless patient Spider Lines: 29 Message-ID: References: <20250308192940.00001351@yahoo.com> <874izvjs4m.fsf@nosuchdomain.example.com> <87senfi7ii.fsf@nosuchdomain.example.com> Injection-Date: Tue, 18 Mar 2025 17:36:29 +0100 (CET) Injection-Info: dont-email.me; posting-host="17e577fd37551b95a778f60cf977438f"; logging-data="3037350"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ZdpJn5mOAcP1RDu3FyVvp" Cancel-Lock: sha1:Pie5fnmoEcYHQ3u6PNk1ul4RpL8= Bytes: 2696 On Tue, 18 Mar 2025 10:59:27 +0000 bart wibbled: >On 18/03/2025 09:53, Muttley@DastardlyHQ.org wrote: >> You'll have to excuse me if I take that figure with a large packet of salt >> unless the code does nothing particularly complicated. > >If you don't believe my figures, try Tiny C on actual C programs. > >Tiny C is single pass, mine does multiple passes so is a little slower. > >What the code does is not that relevant: > >c:\cx\big>tim tcc fann4.c >Time: 0.855 > >c:\cx\big>dir fann4.exe >18/03/2025 10:44 10,491,904 fann4.exe > >So tcc can generate 12MB per second in this case, for a test file of >nearly 1M lines. > >What you should find harder to believe is this figure: > >c:\cx\big>tim gcc fann4.c >Time: 50.571 (44.2 on subsequent build) Without seeing some of the code its impossible to know though I imagine gcc isn't optimised for Windows.