Handle super-method invocations in CPS->JS backend.

pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart

Index: pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart
diff --git a/pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart b/pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart
index 26a0fa57e735e696a91fcfa490e0838bf6abc0bc..7adc39fb50501a0f44d5d99112d8f3f2aebcd573 100644
--- a/pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart
+++ b/pkg/compiler/lib/src/dart_backend/backend_ast_emitter.dart
@@ -777,8 +777,12 @@ class ASTEmitter
   }
 
   @override
-  Expression visitInvokeSuperMethod(tree.InvokeSuperMethod exp,
-                                    BuilderContext<Statement> context) {
+  Expression visitInvokeMethodDirectly(tree.InvokeMethodDirectly exp,
+                                       BuilderContext<Statement> context) {
+    // When targeting Dart, InvokeMethodDirectly is only used for super calls.
+    // The receiver is known to be `this`, and the target method is a method
+    // on the super class. So we just translate it as a method call with the
+    // super receiver.

[sigurdm, 2015/01/20 10:54:25]

Perhaps put asserts here that the invariant is maintained

[asgerf, 2015/01/20 13:07:50]

Unfortunately there is no good way to do that. If the receiver is a variable, we
can't tell if it is initialized to 'this', and I don't want the validity of code
generation to be dependent on optimization.

     return emitMethodCall(exp, new SuperReceiver(), context);
   }