[lwip-devel] [bug #26133] Processor specific porting needs flexibility in terms of placement of various memory pools and heap

[Bill Auerbach]

Follow-up Comment #8, bug #26133 (project lwip):

>Are there any architectures where this doesn't work?

If not, there's not much choice than for the user to change the source code
where the buffers are allocated, right?  You could add to the definitions
LWIP_MEM_XXX_ATTRIBUTE (XXX is the pool name as done with the array name)
before the name and if a compiler comes up that needs it with the definition,
the user can provide this.  It would mean adding LWIP_MEM_XXX_ATTRIBUTE
#defines (set to blank) in cc.h.

At least now GCC ports can use this if needed which supports a significant
lwip user base.  The number of users who will use this feature and the number
of those not using GCC is even smaller.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?26133>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/