[es6] Perform the IsConstructor test in GetSuperConstructor.

src/compiler/bytecode-graph-builder.cc

Index: src/compiler/bytecode-graph-builder.cc
diff --git a/src/compiler/bytecode-graph-builder.cc b/src/compiler/bytecode-graph-builder.cc
index 357837db35f9a4fadab2033d63090e8e34755ad7..e07d014de5598dfa6f7b7660984c4c3b10bb56c2 100644
--- a/src/compiler/bytecode-graph-builder.cc
+++ b/src/compiler/bytecode-graph-builder.cc
@@ -1610,6 +1610,13 @@ void BytecodeGraphBuilder::VisitDeletePropertySloppy() {
   BuildDelete(LanguageMode::SLOPPY);
 }
 
+void BytecodeGraphBuilder::VisitGetSuperConstructor() {
+  Node* node = NewNode(javascript()->GetSuperConstructor(),
+                       environment()->LookupAccumulator());
+  environment()->BindRegister(bytecode_iterator().GetRegisterOperand(0), node,
+                              Environment::kAttachFrameState);

[Henrique Ferreiro, 2016/12/08 13:18:01]

Is attaching the frame state correct? Is it related to the operator throwing
exceptions?

[Benedikt Meurer, 2016/12/08 18:42:24]

Yes and yes :-)

Since this operation can throw an exception we need to be able to construct a
proper stack trace, which is done by looking at the deoptimization information.

+}
+
 void BytecodeGraphBuilder::BuildCompareOp(const Operator* js_op) {
   PrepareEagerCheckpoint();
   Node* left =