From: bc@freeuk.com   
      
   On 28/11/2025 10:41, David Brown wrote:   
      
      
   >  But for   
   > me, -O2 is generally the sweet spot.  I have no real interest in using a   
   > compiler that doesn't do decent optimisation - if I am happy with slow   
   > code, I'll use Python.   
   >   
      
   That's like saying that if you can't go at 100mph, you're happy to walk!   
      
   There's no compromise at all?   
      
   I've taken a task (decode JPEG) which uses the same algorithm across   
   three languages, and applied it to the same input. These are the   
   runtimes, expressed in relative MPH:   
      
                                            Drive 1 mile:   
      gcc -O3  C       108   mph                     33s   
      gcc -O2  C       100   mph                     36s   
      mm       M        77   mph (my lang)           47s   
      bcc      C        55   mph (my product)     1m 05s   
      tcc      C        25   mph                  2m 24s   
      CPython  Python    0.8 mph              1h 15m 00s   
      
   Actually, forget walking: you'd rather crawl on your hands on knees!   
      
   (The figure for PyPy for this task, which has lots of long loops to get   
   stuck into, is 19 mph, but the speedup is generally unpredictable.)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)