Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fine tune the managed heap size definition on reference targets #90

Closed
nfbot opened this issue Aug 30, 2017 · 1 comment
Closed

Fine tune the managed heap size definition on reference targets #90

nfbot opened this issue Aug 30, 2017 · 1 comment

Comments

@nfbot
Copy link
Member

nfbot commented Aug 30, 2017

From nf-interpreter created by josesimoes : nanoframework/nf-interpreter#366

The current definition of the managed heap size (clr_managed_heap_size in each targets\CMSIS-OS\ChibiOS\TTAARRGGEETT_BBOOAARRDD\CMakeLists.txt) is not optimal and for most boards is kind of short.

It's already optimized for Discovery4 target in nanoframework/nf-interpreter#365.
Need to go through the remaining target boards and maximize the size of it.
Suggest that the CRT heap is moved to the CCM (on the targets were available). This happened in #365 for Discovery4 too.

On the boards were the CRT heap shares the same RAM region, make sure the Managed Heap size leaves a fair amount of RAM to the CRT heap.

@josesimoes
Copy link
Member

This has been addressed in nanoframework/nf-interpreter#528.
Instead of optimizing the size of the managed heap, it was made completely automatic in the linking stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants