From: bc@freeuk.com   
      
   On 30/10/2025 14:13, Scott Lurndal wrote:   
   > antispam@fricas.org (Waldek Hebisch) writes:   
   >> bart  wrote:   
   >>> On 29/10/2025 23:04, David Brown wrote:   
   >>>> On 29/10/2025 22:21, bart wrote:   
   >   
   >>>   
   >>> BTW 68Kloc would be CDECL; and 78Kloc is A68G. The CDECL timings are:   
   >>>   
   >>>    root@DESKTOP-11:/mnt/c/Users/44775/Downloads/cdecl-18.5# time make   
   >>>> output   
   >>>       
   >>>    real    0m49.512s   
   >>>    user    0m19.033s   
   >>>    sys     0m3.911s   
   >>   
   >> Those numbers indicate that there is something wrong with your   
   >> machine.  Sum of second and third line above give CPU time.   
   >> Real time is twice as large, so something is slowing down things.   
   >> One possible trouble is having too small RAM, then OS is swaping   
   >> data to/from disc.  Some programs do a lot of random I/O, that   
   >> can be slow on spinning disc, but SSD-s usually are much   
   >> faster at random I/O.   
   >>   
   >> Assuming that you have enough RAM you should try at least using   
   >> 'make -j 3', that is allow make to use up to 3 jobs.  I wrote   
   >> at least, because AFAIK cheapest PC CPU-s of reasonable age   
   >> have at least 2 cores, so to fully utilize the machine you   
   >> need at least 2 jobs.  3 is better, because some jobs may wait   
   >> for I/O.   
   >>   
   >> FYI, reasonably typical report for normal make (without -j   
   >> option) on my machine is:   
   >>   
   >> real	0m4.981s   
   >> user	0m3.712s   
   >> sys	0m0.963s   
   >>   
   >   
   > Just for grins, here's a report for a full rebuild of a real-world project   
   > that I build regularly.  Granted most builds are partial (e.g. one or   
   > two source files touched) and take far less time (15 seconds or so,   
   > most of which is make calling stat(2) on a few hundred source files   
   > on an NFS filesystem).  Close to three million SLOC, mostly in header   
   > files. C++.   
      
      
   What is the total size of the produced binaries? That will me an idea of   
   the true LoC for the project.   
      
   How many source files (can include headers) does it involve? How many   
   binaries does it actually produce?   
      
   > $ time make -s -j96   
   > real    9m10.38s   
   > user    3h50m15.59s   
   > sys     9m58.20s   
   >   
   > I'd challenge Bart to match that with a similarly sized project using   
   > his compiler and toolset, but I seriously doubt that this project could   
   > be effectively implemented using his personal language and toolset.   
      
   If what you are asking is how my toolset can cope with a project on this   
   scale, then I can have a go at emulating it, given the information above.   
      
   I can tell you that over 4 hours, and working at generating 3-5MB per   
   second, my compiler could produce 40-70GB of binary code in that time,   
   although not in one file due to memory. I guess the size is somewhat   
   smaller than that.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)