From a5ad2059821b86ef26a86d78c40cc680c57aa94e Mon Sep 17 00:00:00 2001
From: Alasdair Armstrong
Date: Wed, 29 Aug 2018 18:01:50 +0100
Subject: C: Fix some issues with tuples as arguments to polymorphic
 constructors

Now all we need to do is make sure the RISC-V builtins are mapped to
the correct C functions, and RISC-V in C should work
(hopefully). We're still missing some of the functions in sail.c for
the mappings so those have to be implemented.
---
 src/bytecode_util.ml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/bytecode_util.ml')

diff --git a/src/bytecode_util.ml b/src/bytecode_util.ml
index 4ddb0c81..7bad6d0b 100644
--- a/src/bytecode_util.ml
+++ b/src/bytecode_util.ml
@@ -166,7 +166,7 @@ let rec string_of_fragment ?zencode:(zencode=true) = function
   | F_have_exception -> "have_exception"
   | F_current_exception -> "(*current_exception)"
   | F_raw raw -> raw
-  | F_poly f -> "POLY(" ^ string_of_fragment ~zencode:zencode f ^ ")"
+  | F_poly f -> string_of_fragment ~zencode:zencode f
 and string_of_fragment' ?zencode:(zencode=true) f =
   match f with
   | F_op _ | F_unary _ -> "(" ^ string_of_fragment ~zencode:zencode f ^ ")"
-- 
cgit v1.2.3