kaspar/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-12-15 01:23:49 +01:00
Code Releases Activity

doc/guides/misc/dev_best_practices: remove outdated MSP430 info

Browse Source 
Co-authored-by: Marian Buschsieweke <maribu@users.noreply.github.com>
This commit is contained in:
AnnsAnn 2025-09-18 14:01:53 +02:00
parent 559de70abb
commit ae420f6bb4
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/guides/misc/dev_best_practices.md
View File

@ -145,7 +145,5 @@ If you want to analyze the static memory consumption of your code you can use
* Code can request the amount of memory it needs on runtime
* On most platforms: the size of the heap is `sizeof(<RAM>)-sizeof(<static memory>)`
* If you reduce your usage of static memory your heap gets bigger
* On some platforms calling `free()` will not or not always make heap memory available again
(see [Oneway Malloc on MSP430](https://doc.riot-os.org/group__oneway__malloc.html))
* Programmer needs to handle failed memory allocation calls at runtime
* Static code analysis is unable to find errors regarding memory management