home bbs files messages ]

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,729 of 243,242   
   bart to Scott Lurndal   
   Re: New and improved version of cdecl   
   31 Oct 25 14:55:49   
   
   From: bc@freeuk.com   
      
   On 31/10/2025 13:57, Scott Lurndal wrote:   
   > bart  writes:   
   >> On 30/10/2025 16:22, Scott Lurndal wrote:   
   >>> bart  writes:   
   >   
   >>>>   
   >>>> What is the total size of the produced binaries?   
   >>>   
   >>> There are 181 shared objects (DLL in windows speak) and   
   >>> six binaries produced by the build.   The binaries are all quite small   
   since   
   >>> they dynamically link at runtime with the necessary   
   >>> shared objects, the set of which can vary from run-to-run.   
   >>>   
   >>> The largest shared object is 7.5MB.   
   >>>   
   >>>      text    data     bss     dec     hex filename   
   >>> 6902921  109640 1861744 8874305  876941 lib/libXXX.so   
   >>   
   >> Well, I've done a couple of small tests.   
   >   
   > Pointlessly.   
   >   
   >>   
   >> The first was in generating 200 'small' DLLs - duplicates of the same   
   >> library. This took 6 seconds to produce 200 libraries of 50KB each (10MB   
   >> total). Each library is 5KB as it includes my language's standard libs.   
   >   
   > The shared object 'text' size ranges from 500KB to 14MB.   
      
   Well, I asked for some figures, and they were lacking. And here, the   
   14MB figure contradicts the 7.5MB you mentioned above as the largest object.   
      
      
   > Your toy projects aren't representative of real world application   
   > development.  Can you not understand that?   
      
   I don't believe you. Clearly my tests show that basic conversion of HLL   
   code to native code can be easily done at several MB per second even on   
   my low-end hardware - per core.   
      
   If your tests have a effective throughput far below that, then either   
   you have very slow compilers, or are doing a mountain of work unrelated   
   to compiling, or the orchestration of the whole process is poor, or some   
   combination.   
      
   (You mentioned there are nearly 400 developers involved? It sounds like   
   a management problem.   
      
   Perhaps you should employ someone whose job it is to look at the big   
   picture, and to get those iteration times down.)   
      
   In any case, the tasks I want to build are nothing like that, yet there   
   is at least 2 magnitudes difference in build-time between my 'toy'   
   tools, and all that Unix stuff that you are all trying to force down my   
   throat.   
      
   --- 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