Changes for running tests on arm64 hardware.

runtime/vm/runtime_entry_arm64.cc

Index: runtime/vm/runtime_entry_arm64.cc
===================================================================
--- runtime/vm/runtime_entry_arm64.cc	(revision 37032)
+++ runtime/vm/runtime_entry_arm64.cc	(working copy)
@@ -40,10 +40,18 @@
   if (is_leaf()) {
     ASSERT(argument_count == this->argument_count());
     ExternalLabel label(entry);
-    // Cache the stack pointer in a callee-saved register.
+    // Since we are entering C++ code, we must restore the C stack pointer from
+    // the stack limit to an aligned value nearer to the top of the stack.
+    // We cache the Dart stack pointer and the stack limit in callee-saved
+    // registers, then align and call, restoring CSP and SP on return from the
+    // call.
+    __ mov(R25, CSP);
     __ mov(R26, SP);

[regis, 2014/06/05 17:55:34]

R25 and R26 are callee-saved and will thus be preserved by the leaf call. But
how do you know they are available and not currently used by the calling Dart
code?

[zra, 2014/06/05 18:35:53]

Before IL instructions with a kCall LocationSummary, the compiler spills the
live registers. We don't have any leaf runtime calls outside of these IL
instructions.

+    __ ReserveAlignedFrameSpace(0);
+    __ mov(CSP, SP);
     __ BranchLink(&label, kNoPP);
     __ mov(SP, R26);
+    __ mov(CSP, R25);
   } else {
     // Argument count is not checked here, but in the runtime entry for a more
     // informative error message.