You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the free function does not include any dynamic memory. It just includes the bss section (static memory using __bss_end) and the stack. Even though bitlash itself doesn't use dynamic memory, sketches may and this should be accounted for in the free output. The func_free implementation already links to a page that does this, using the __brkval variable.
The text was updated successfully, but these errors were encountered:
It’s a fair point. There was literally not room for such luxuries in the '168 version but we can be somewhat less stingy now.
-br
On Mar 7, 2014, at 5:43 AM, Matthijs Kooijman [email protected] wrote:
The current implementation of the free function does not include any dynamic memory. It just includes the bss section (static memory using __bss_end) and the stack. Even though bitlash itself doesn't use dynamic memory, sketches may and this should be accounted for in the free output. The func_free implementation already links to a page that does this, using the __brkval variable.
—
Reply to this email directly or view it on GitHub.
The current implementation of the
free
function does not include any dynamic memory. It just includes the bss section (static memory using__bss_end
) and the stack. Even though bitlash itself doesn't use dynamic memory, sketches may and this should be accounted for in thefree
output. Thefunc_free
implementation already links to a page that does this, using the__brkval
variable.The text was updated successfully, but these errors were encountered: