Unlimited objects patch from Chris Johns <ccj@acm.org>. Email follows:

    First, the unlimited patch. I have compiled the unlmited patch for the
    Linux posix BSP only and it seems to work cleanly. I would like a really
    major application run on this change before commiting as the changes are
    very core and significant. I am currently building all the tests to run.

    I have no targets suitable to test on at the moment.

    I have tested the patch for inline functions and macros.

    Turning macros on has found some core bugs. I have fixed these but have
    not run all the tests. Please review the patch for these changes. They
    are:

    1) The conditional compilation for MP support broke the core messages
    code. You cannot embed a conditional macro in another macro. The Send
    and Urgent Send calls are macros.

    2) User extensions handler initialisation now has two parameters. I have
    updated the macros to support the extra parameter.

    The patch also contains the gcc-target-default.cfg fix required to build
    the kernel. More of a by product than a fix for you.

1 files changed, 37 insertions, 0 deletions

diff --git a/testsuites/samples/unlimited/unlimited.doc b/testsuites/samples/unlimited/unlimited.doc
new file mode 100644
index 0000000000..aad9af7f8a
--- /dev/null
+++ b/testsuites/samples/unlimited/unlimited.doc
@@ -0,0 +1,37 @@
+#
+#  $Id$
+#
+#  COPYRIGHT (c) 1989-1997.
+#  On-Line Applications Research Corporation (OAR).
+#  Copyright assigned to U.S. Government, 1994.
+#
+#  The license and distribution terms for this file may in
+#  the file LICENSE in this distribution or at
+#  http://www.OARcorp.com/rtems/license.html.
+#
+
+This file describes the directives and concepts tested by this test set.
+
+test set name:  test1
+
+directives:
+  _Object_Allocate, _Object_Free, _Object_Extend_information, 
+  _Object_Shrink_information
+
+concepts:
+
+  a.  Verifies when the auto-extend is false the number of objects does
+      not grow, and the number of objects is the maximum number specified
+      in the Configuration table.
+
+  b.  Verify the re-allocation of index numbers, and a block of objects is
+      freed while another remains yet all it objects are not in
+      use. Four blocks of the allocation size of objects are created,
+      then the first and third blocks are freed. Only the first
+      block's memory will be released, while the second remains. This
+      is due the allocation hystersis.
+
+  c.  Allocate as many objects are the work-space can hold. Free objects
+      from a number of blocks with-out freeing the blocks. Free the remaining
+      blocks.
+