Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c    |    Meh, in C you gotta define EVERYTHING    |    243,242 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 241,717 of 243,242    |
|    bart to bart    |
|    Re: New and improved version of cdecl    |
|    31 Oct 25 02:14:00    |
      From: bc@freeuk.com              On 30/10/2025 23:49, bart wrote:       > On 30/10/2025 15:04, David Brown wrote:       >> On 30/10/2025 13:07, bart wrote:       >       >> Maybe there /is/ something wrong with your machine or setup. If you       >> have a 2 core machine, it is presumably a low-end budget machine from       >> perhaps 15 years ago. I'm all in favour of keeping working systems       >> and I strongly disapprove of some people's two or three year cycles       >> for swapping out computers, but there is a balance somewhere. With       >> such an old system, I presume you also have old Windows (my office       >> Windows machine is Windows 7), and thus the old and very slow style of       >> WSL. That, I think, could explain the oddities in your timings.       >       > The machine is from 2021. It has an SSD, 8GB, and runs Windows 11. It       > uses WSL version 2.       >       > It is fast enough for my 40Kloc compiler to self-host itself repeatedly       > at about 15Hz (ie. produce 15 new generations per second). And that is       > using unoptimised x64 code:       >       > c:\mx2>tim ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms hello       > Hello, World       > Time: 1.017       >       > Hmm, I'm only counting 14 'ms' after the first. So apologies, it is only       > 14Hz!              That timing is from the current compiler. The more streamlined one I'm       working on now (where the IL plays a smaller role) can manage 16Hz; 14%       faster.              There are a few sluggish areas I want to look at.              And yes it is more of a sport now than a real need.              My compilers ought to be slow as they have so many passes. Tcc       supposedly has only one. So another project I might have a go at is a       single-pass C compiler that is faster than Tcc.              Just to see how fast I can go at producing native code. However, if the       code is too poor, there will be lots of it, and it will slow down the       latter stages. I'll have to see.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca