#2790: Use -fregs-graph by default
---------------------------------+------------------------------------------
    Reporter:  igloo             |        Owner:  benl            
        Type:  task              |       Status:  assigned        
    Priority:  high              |    Milestone:  6.12.1          
   Component:  Compiler          |      Version:  6.8.3           
    Severity:  normal            |   Resolution:                  
    Keywords:                    |   Difficulty:  Unknown         
    Testcase:                    |           Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
---------------------------------+------------------------------------------
Comment (by Roel van Dijk):

 I'll comment on this ticket since all related tickets refer to this one.

 When building the [http://hackage.haskell.org/package/encoding-0.6.2
 encoding-0.6.2] package with library profiling enabled GHC panics on the
 rather large (1010547 bytes) file
 [http://hackage.haskell.org/packages/archive/encoding/0.6.2/doc/html/Data-
 Encoding-GB18030.html Data.Encoding.GB18030] which is a Chinese character
 encoding.

 GHC panics with both the linear allocator and the graph colouring one.

 With linear allocator:

 {{{
 [40 of 65] Compiling Data.Encoding.GB18030 (
 dist/build/Data/Encoding/GB18030.hs, dist/build/Data/Encoding/GB18030.p_o
 )
 ghc: panic! (the 'impossible' happened)
   (GHC version 6.10.4 for i386-unknown-linux):
         RegAllocLinear.getStackSlotFor: out of stack slots, try -fregs-
 graph
 }}}

 With register graph colouring:

 {{{
 [40 of 65] Compiling Data.Encoding.GB18030 (
 dist/build/Data/Encoding/GB18030.hs, dist/build/Data/Encoding/GB18030.p_o
 )
 ghc: panic! (the 'impossible' happened)
   (GHC version 6.10.4 for i386-unknown-linux):
         regSpill: out of spill slots!
        regs to spill = 800
        slots left    = 677
 }}}

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2790#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to