Are Memory Pools allowed by MISRA-C?

[jpature]

Hi,

Would a memory pool (to handle a variable number of objects) based on a statically allocated chunk of memory be MISRA C compliant ? Or would it be banned because considered as dynamic allocation ?

Thanks.

[Francois]

Hi,
I'm also interested in this question.
If you create your own sw component, your design can be predictable, controlled and secured. UT proof can also be provided.
Also, you will not use heap in this case.
It is ok for me, but let's wait for misra-c answer

[jpature]

Hi,
I'm also interested in this question.
If you create your own sw component, your design can be predictable, controlled and secured. UT proof can also be provided.
Also, you will not use heap in this case.
It is ok for me, but let's wait for misra-c answer

Hi,
I agree with it, thus my question 

---

Could anyone help answer this question?
Thanks

[misra-c]

As a holding answer...

The problems with dynamic memory allocation are numerous, particularly with regards fragmentation and error checking.

It also depends on what you mean by "memory pool" - for example, a fixed-sized array of objects, but where the number of used elements depends on the particular build configuration, would probably be OK.

Of course, any REQUIRED Rule may be deviated if necessary - but the onus is then on the user to justify the deviation and have appropriate sign off.