Does TSK_delete() call MEM_free() to free the stack in both cases?

Hi Judah,

That is what I thought too, at first. However, upon later inspection of the TSK_Attrs struct (please find quoted below), I found that there actually exists a field called "stackseg" (along with "stacksize" and the "stack" pointer itself). So, technically, TSK_delete() should be able to do MEM_free() in both cases, like the manual suggests.

The question is: Is it a correct interpretation of the manual that MEM_free() actually is called in both cases, and does TSK_delete() actually do that properly?

C.f. "TMS320C6000 DSP/BIOS 5.x API Reference Guide" (SPRU403r) p. 2-536:

struct TSK_Attrs { /* task attributes */
        Int priority; /* execution priority */
        Ptr stack; /* pre-allocated stack */
        size_t stacksize; /* stack size in MADUs */
        Int stackseg; /* mem seg for stack alloc */
        Ptr environ; /* global environ data struct */
        String name; /* printable name */
        Bool exitflag; /* prog termination requires */
        /* this task to terminate */
        Bool initstackflag; /* initialize task stack? */
};

All the best,
Fredrik

Fredrik,

How it works is that if you specify the "stack" field then "stackseg" is set to -1 and doesn't come into play.  Only when "stack" is null that we use "stackseg" for allocating the stack.  So, what I said in my previous post still holds true.

Judah

Hi Judah,

OK, thank you very much. Perhaps the manual could clarify these points and describe the interplay between the stack fields in more detail.

Many thanks,
Fredrik

Hi Judah,

Would bios.TSK.DELETEFXN be the proper place to call MEM_free for the stack?

All the best,
Fredrik