Bug 353259

Description Dave Russo 2011-07-27 19:15:36 EDT

As it stands today, Mod_construct() throws an error when used in a static only system:
    o both Mod_create() and Mod_construct() reference a configuration generated
      function 
    o in static only configurations this generated function simply throws an 
      error
    o in create or delete policy configurations this generated function call
      first calls xdc.runtime.Core.createObject() then calls the module's 
      instance init function

To support modules that want to allow construct to be used in static-only systems we can:
    o add a @StaticConstruct attribute to the module spec language
    o static-only configurations, change the config generated create functions
      for modules with this new attribute during to 
          1. throw an error if NULL is passed for the object's space
          2. call a simpler xdc.runtime.Core.constructObject() which has no
             reference to Memory allocation functions, but
          3. otherwise behaves identically to the function currently generated 
             for create-policy configurations.
    o for all other configurations, the generated create functions would be
      unchanged from it's current implementation.

We can avoid adding the @StaticConstruct attribute if we are willing to accept larger configuration generated big.c files for static-only systems.