separate compilation for library profiling
 
            
            
            
            
                5 Jan
                
                    2020
                
            
            
                5 Jan
                
                '20
                
            
            
            
        
    
                5:52 a.m.
            
        Why does GHC start a separate compilation when I build with cabal --enable-library-profiling? At least parsing and type-checking should be the same as in the non-profiling compilation. Why aren't these steps shared between profiling and non-profiling compilation? I remember that in the past GHC also started a separate compilation for shared object generation. However, starting with GHC-7.8 dyn-files are just generated along with static compilation.
        2126
        
      
          Age (days ago)
        
      
        2126
        
    
          Last active (days ago)
        
        
        
        0 comments
    
    
        
        1 participants
    
    
    
    
    
    
    
    
    participants (1)
- 
                 Henning Thielemann Henning Thielemann