Opened 10 years ago

Closed 9 years ago

#3554 closed bug (fixed)

ASSERT failed! file TcMType.lhs line 349

Reported by: simonmar Owned by: chak
Priority: normal Milestone: 7.0.1
Component: Compiler (Type checker) Version: 6.10.4
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case: indexed-types/should_fail/T2627b
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Description

Test T2627b is failing with an assertion failure with a DEBUG compiler:

=====> T2627b(normal)
cd ./indexed-types/should_fail && '/64playpen/buildbot/x86_64-linux-head/build/inplace/bin/ghc-stage2' -fforce-recomp -dcore-lint -dcmm-lint -no-user-package-conf  -dno-debug-output -c T2627b.hs    >T2627b.comp.stderr 2>&1
Actual stderr output differs from expected:
--- ./indexed-types/should_fail/T2627b.stderr.normalised	2009-09-29 21:47:01.000000000 +0100
+++ ./indexed-types/should_fail/T2627b.comp.stderr.normalised	2009-09-29 21:47:01.000000000 +0100
@@ -1,8 +1,7 @@
+ghc: panic! (the 'impossible' happened)
+  (GHC version 6.13.20090929 for x86_64-unknown-linux):
+	ASSERT failed! file TcMType.lhs line 349
+t_aju{tv} [tau]
+

Change History (5)

comment:1 Changed 10 years ago by chak

This is one of the remaining cases, where a type variable is instantiated twice, due to the current imperfect interaction between the equality solver and the rest of TcSimplify. This will probably only get fixed once we have the new implementation of implications constraints.

comment:2 Changed 9 years ago by igloo

Milestone: 6.12.26.14.1
Type of failure: None/Unknown

comment:3 Changed 9 years ago by igloo

Blocked By: 4232 added

comment:4 Changed 9 years ago by simonpj

Resolution: fixed
Status: newclosed
Test Case: T2627bindexed-types/should_fail/T2627b

This is fine with the new typechecker.

comment:5 Changed 9 years ago by igloo

Blocked By: 4232 removed
Note: See TracTickets for help on using tickets.