Heap access/memory management.

[JerryHRoss]

To use this compiler to build an RTOS like FreeRTOS, the developer needs access to the remaining free RAM/heap. Access to the addresses of the beginning and end of free RAM is required and at least malloc and free functions to allow for dynamic allocation and freeing of memory.

Granted, I could allocate a large array of bytes and write my own malloc and free functions but that is problematic in that it requires adjusting the size of the array as RAM usage increases with added features/functionality. Not to mention managing heap fragmentation, etc.

It would be much better if the compiler/library functions took care of those issues.

Any chance of this happening soon?

[milutin.apostolovic]

Hi,

It is under consideration.
Thank you for your feedback.


Best regards.

[JerryHRoss]

Oh! I forgot: another need is the ability to flag a function (with a pragma? or keyword "task") that tells the compiler not to create a stack frame for that function.

[mileta.miletic]

Hi,
Thanks for suggestion, but this is not planned for implementation.

[Anuradha]

Hi,

It is under consideration.
Thank you for your feedback.


Best regards.

Is it implemented now.

How can i use malloc() function with MikroC PRO for pic.

Thank you