[PATCH] score: Change _Heap_Extend() API

[Joel Sherrill]

On 08/09/2012 07:36 AM, Sebastian Huber wrote:
> On 08/09/2012 02:24 PM, Joel Sherrill wrote:
>> How about a better name?:)
> A better name for _Heap_Extend_4()?
Yes. Since the 4 appears to indicate something about the
fourth parameter. Not the best choice of names.
>> Can this just replace the regular _Heap_Extend usage and then we
>> can use that name?
> We can also use _Heap_Extend() with an unused 4th parameter.
If that works for the current use case(s), then I think it is better.
No need to have more code.
> The background for this work is that I want to change the workspace and heap
> initialization.  I need more flexibility to support controllers with several
> different memory areas.
>
I assumed you had a good reason. It was too early for me to remember
you see controllers with multiple non-contiguous RAM areas.

How's the coverage? Or do you want me to do a new run of at
least -Os, POSIX disabled, core once this settles?


-- 
Joel Sherrill, Ph.D.             Director of Research&   Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
     Support Available             (256) 722-9985