See this Source Code
The referenced C++ code above points at where the assembly function call is made for _x_alloc. Currently, that call is withheld from the cross compiler's generated assembly files, because there is no backend definition for _x_alloc yet. Once that is authored, the addInstruction() procedure call on L59 (of the above file) should be uncommented. Once that is done, memory will be dynamically allocating correctly (albeit unoptimized) and data types can continue in development.
See this Source Code
The referenced C++ code above points at where the assembly function call is made for
_x_alloc. Currently, that call is withheld from the cross compiler's generated assembly files, because there is no backend definition for_x_allocyet. Once that is authored, theaddInstruction()procedure call on L59 (of the above file) should be uncommented. Once that is done, memory will be dynamically allocating correctly (albeit unoptimized) and data types can continue in development.