#6151 closed bug (fixed)

typePrimRep: UbxTupleRep

Reported by: simonmar Owned by:
Priority: highest Milestone: 7.6.1
Component: Compiler Version: 7.5
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

A handful of new failures appeared in the nightly build recently, perhaps as a result of the changes to unboxed tuple handling. The failures are all with GHCi.

e.g.

'/64playpen/simonmar/nightly/HEAD-cam-04-unx/x86_64-unknown-linux/inplace/bin/ghc-stage2' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-conf -rtsopts  -fno-ghci-history cgrun064.hs --interactive -ignore-dot-ghci +RTS -I0.1 -RTS    
GHCi, version 7.5.20120607: http://www.haskell.org/ghc/  :? for help
Loading package ghc-prim ... linking ... done.
Loading package integer-gmp ... linking ... done.
Loading package base ... linking ... done.
[1 of 1] Compiling Main             ( cgrun064.hs, interpreted )
ghc-stage2: panic! (the 'impossible' happened)
  (GHC version 7.5.20120607 for x86_64-unknown-linux):
        typePrimRep: UbxTupleRep
    (# ghc-prim:GHC.Prim.State#{(w) tc 32q} s{tv v} [tv],
       ghc-prim:GHC.Prim.MutableArray#{(w) tc 31m}
         s{tv v} [tv] a{tv u} [tv] #)

The full set of failures is:

   array/should_run                        arr020 [bad stdout or stderr] (ghci)
   codeGen/should_run                      cgrun064 [bad stdout or stderr] (ghci)
   codeGen/should_run                      cgrun065 [bad stdout or stderr] (ghci)
   codeGen/should_run                      cgrun068 [bad stdout or stderr] (ghci)
   codeGen/should_run                      cgrun070 [bad stdout or stderr] (ghci)

Change History (1)

comment:1 Changed 23 months ago by batterseapower

  • Resolution set to fixed
  • Status changed from new to closed

I think I fixed this with my commit ad6af5fc6db334a373ef3b7cca72143a8bf6b459

I'm still getting some validate failures (see below) but I can reproduce them with the commit directly before my unboxed-tuple branch was merged in, so I think they are unrelated to my changes:

Unexpected failures:
   concurrent/should_run  conc070 [bad exit code] (ghci)
   ghci/prog001           prog001 [bad exit code] (ghci)
   ghci/prog003           prog003 [bad exit code] (ghci)
   ghci/scripts           T6106 [bad exit code] (ghci)
   ghci/scripts           ghci038 [bad exit code] (ghci)
   ghci/should_run        3171 [bad stdout] (normal)
   perf/compiler          T1969 [stat not good enough] (normal)
   perf/compiler          T4801 [stat too good] (normal)
   perf/compiler          T5321Fun [stat not good enough] (normal)
   perf/compiler          T783 [stat not good enough] (normal)
Note: See TracTickets for help on using tickets.