Add 'fixnum' library to utils/

tests/lib/lib.status

Index: tests/lib/lib.status
diff --git a/tests/lib/lib.status b/tests/lib/lib.status
index 29f18dd289637d1516409e1ee1a6efeaf8220105..324a298bb7c51a7d5657a5660a44daddad5321d4 100644
--- a/tests/lib/lib.status
+++ b/tests/lib/lib.status
@@ -2,6 +2,13 @@
 # for details. All rights reserved. Use of this source code is governed by a
 # BSD-style license that can be found in the LICENSE file.
 
+# Run this test manually to verify that the fixnum library produces
+# the same results as native ints on a set of directed and random inputs.
+# Skip it when runnimng automated tests because it times out.  This
+# test only makes sense on runtimes that support 64-bit integer
+# arithmetic natively, i.e., the VM.
+fixnum/int_64_vm_test: Skip

[Mads Ager (google), 2012/06/14 14:57:22]

Thanks for adding the comment. Does it make sense (in a follow-up change) to
scale down the test with fewer cases and always run it on the VM? Then the
manual step could be to change something in the test file itself to go through
the full set of tests?

+
 [ $compiler == frog ]
 crypto/*: Skip