dongsheng28849455 ba59e56e19 User defined memory allocator for different purposes (#3316) ... Some issues are related with memory fragmentation, which may cause the linear memory cannot be allocated. In WAMR, the memory managed by the system is often trivial, but linear memory usually directly allocates a large block and often remains unchanged for a long time. Their sensitivity and contribution to fragmentation are different, which is suitable for different allocation strategies. If we can control the linear memory's allocation, do not make it from system heap, the overhead of heap management might be avoided. Add `mem_alloc_usage_t usage` as the first argument for user defined malloc/realloc/free functions when `WAMR_BUILD_ALLOC_WITH_USAGE` cmake variable is set as 1, and make passing `Alloc_For_LinearMemory` to the argument when allocating the linear memory.		2024-04-18 19:40:57 +08:00
..
deps	Separate app-manager and app-framework from WAMR (#3129)	2024-02-20 18:12:36 +08:00
iwasm	User defined memory allocator for different purposes (#3316)	2024-04-18 19:40:57 +08:00
shared	Fix posix_fadvise error handling (#3323)	2024-04-17 16:06:25 +08:00
config.h	User defined memory allocator for different purposes (#3316)	2024-04-18 19:40:57 +08:00
version.h	Update version number to 1.3.2 and update release notes (#3083)	2024-02-01 12:42:12 +08:00