Re: [GHC] #7534: allocateRegsAndSpill: Cannot read from uninitialized register
#7534: allocateRegsAndSpill: Cannot read from uninitialized register --+- Reporter: erikd | Owner: simonmar Type: bug| Status: infoneeded Priority: normal | Milestone: Component: Compiler | Version: 7.7 Keywords: | Os: Linux Architecture: powerpc64 | Failure: Building GHC failed Difficulty: Unknown|Testcase: Blockedby: |Blocking: Related: | --+- Changes (by simonmar): * status: new = infoneeded Comment: More info needed to make progress on this one, the repro case only happens on PPC/Linux. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7534#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #7534: allocateRegsAndSpill: Cannot read from uninitialized register
#7534: allocateRegsAndSpill: Cannot read from uninitialized register --+- Reporter: erikd | Owner: simonmar Type: bug| Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.7 Keywords: | Os: Linux Architecture: powerpc64 | Failure: Building GHC failed Difficulty: Unknown|Testcase: Blockedby: |Blocking: Related: | --+- Comment(by simonmar): So the background is that this panic used to be commented out, but I enabled it recently because it makes debugging much easier (with the panic commented out, the compiler will happily generate completely bogus code that will crash at runtime). However, it adds another invariant, as mentioned in the comment: all register must be written before they are read (not an unreasonable assumption, I'm sure you'll agree) I presume this invariant is being violated somewhere. To debug it you'll need to use `-ddump-cmm` and find out where the bogus code comes from. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7534#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #7534: allocateRegsAndSpill: Cannot read from uninitialized register
#7534: allocateRegsAndSpill: Cannot read from uninitialized register --+- Reporter: erikd | Owner: simonmar Type: bug| Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.7 Keywords: | Os: Linux Architecture: powerpc64 | Failure: Building GHC failed Difficulty: Unknown|Testcase: Blockedby: |Blocking: Related: | --+- Changes (by simonpj): * owner: = simonmar * difficulty: = Unknown Comment: Simon M, could this be anything to do with the new codegen path? I'll asssign it to you for now. Simon -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7534#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #7534: allocateRegsAndSpill: Cannot read from uninitialized register
#7534: allocateRegsAndSpill: Cannot read from uninitialized register +--- Reporter: erikd| Owner: Type: bug | Status: new Priority: normal | Component: Compiler Version: 7.7 | Keywords: Os: Linux| Architecture: powerpc64 Failure: Building GHC failed | Blockedby: Blocking: |Related: +--- Changes (by PHO): * cc: pho@… (added) -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7534#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #7534: allocateRegsAndSpill: Cannot read from uninitialized register
#7534: allocateRegsAndSpill: Cannot read from uninitialized register +--- Reporter: erikd| Owner: Type: bug | Status: new Priority: normal | Component: Compiler Version: 7.7 | Keywords: Os: Linux| Architecture: powerpc64 Failure: Building GHC failed | Blockedby: Blocking: |Related: +--- Comment(by erikd): From `compiler/nativeGen/RegAlloc/Linear/Main.hs`: {{{ -- NOTE: if the input to the NCG contains some -- unreachable blocks with junk code, this panic -- might be triggered. Make sure you only feed -- sensible code into the NCG. In CmmPipeline we -- call removeUnreachableBlocks at the end for this -- reason. }}} -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7534#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs