jit floor_n

not sure if round mode 9 is actually correct. The compiler explorer claims that's what gcc gives for `(double) round(foo)`. I only see values 0 through 3 explained on the 'net.
MoarVM · Apr 8, 2018 · a206cd8 · a206cd8
1 parent fa16746
commit a206cd8
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/src/jit/graph.c b/src/jit/graph.c
@@ -1513,6 +1513,7 @@ static MVMint32 consume_ins(MVMThreadContext *tc, MVMJitGraph *jg,
     case MVM_OP_div_n:
     case MVM_OP_neg_n:
         /* number coercion */
+    case MVM_OP_floor_n:
     case MVM_OP_coerce_ni:
     case MVM_OP_coerce_in:
     case MVM_OP_extend_i32:

diff --git a/src/jit/x64/emit.dasc b/src/jit/x64/emit.dasc
@@ -1106,6 +1106,14 @@ void MVM_jit_emit_primitive(MVMThreadContext *tc, MVMJitCompiler *compiler, MVMJ
         | movsd qword WORK[reg_a], xmm0;
         break;
     }
+    case MVM_OP_floor_n: {
+        MVMint16 dst = ins->operands[0].reg.orig;
+        MVMint16 src = ins->operands[1].reg.orig;
+        | movsd xmm0, qword WORK[src];
+        | roundsd xmm0, xmm0, 9;
+        | movsd qword WORK[dst], xmm0;
+        break;
+    }
     case MVM_OP_coerce_in: {
         MVMint16 dst = ins->operands[0].reg.orig;
         MVMint16 src = ins->operands[1].reg.orig;