i386 jit print_s

Well I found out the reason for 13 out of the 15 core dumping tests for
'testj' but I'm not sure why this was done:

RCS file: /home/perlcvs/parrot/jit/i386/core.jit,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -p -r1.14 -r1.15
--- parrot/jit/i386/core.jit	2002/01/31 02:22:00	1.14
+++ parrot/jit/i386/core.jit	2002/01/31 03:20:42	1.15
@@ -1,7 +1,7 @@
 ;
 ;   i386_core.jit
 ;
-; $Id: core.jit,v 1.14 2002/01/31 02:22:00 grunblatt Exp $
+; $Id: core.jit,v 1.15 2002/01/31 03:20:42 grunblatt Exp $
 ;

 Parrot_noop {
@@ -65,9 +65,9 @@ Parrot_print_sc {

 Parrot_print_s {
     movl $1,&TEMP_INT[1]
-    cmp $0,&STRING_REG[1]
-    je ($0x0)
-    JUMP(END)
+#    cmp $0,&STRING_REG[1]
+#    je ($0x0)
+#    JUMP(END)
     F(get_bufstart, &STRING_REG[1])
     movl %eax,&TEMP_INT[0]
     F(get_strlen, &STRING_REG[1])


I couldn't find anything on the list - if this is to stay for the time
being perhaps we ought to skip the failing tests if we are doing 'testj' ?

/J\
-- 
Jonathan Stowe                      |
<http://www.gellyfish.com>          |      This space for rent
                                    |

• i386 jit print_s by Jonathan Stowe
• Re: i386 jit print_s by Dan Sugalski