Unnamed repository; edit this file 'description' to name the repository. https://gitea.privatedns.org/xavi/tinyalloc/atom?h=master 2025-11-11T23:42:32+00:00 2025-11-11T23:42:32+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-11-11T23:42:32+00:00 urn:sha1:e32da5559962c6131e1f933a245526d699d45cf6 When reallocating a buffer to one with a smaller size, the number of elements to be copied to the new buffer must not be that of the old buffer, or the behaviour is undefined. 2025-11-11T23:37:51+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-11-11T23:37:51+00:00 urn:sha1:07bff5530cf22d95b98139063ab50cabb8cabe76 This allocator was not designed for reallocations, and therefore prev->size cannot be extended because that would overlap its contents with other data. Because of this, the only safe way to achieve a reallocation is to always allocate a new block, copy any existing data and free the old block. 2025-11-10T22:50:41+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-11-10T22:50:41+00:00 urn:sha1:fd8128d9b84e362abdbd05fafe252421edee8ab2 So far, tinyalloc was designed for a static heap area, failing to allocate whenever the end boundary was reached. Unfortunately, this design was too limiting if the same library were to be used for WebAssembly applications, where interpreters are required to implement the current_memory and grow_memory operators. [1] Whereas the former returns the number of currently allocated pages by the interpreter (64 KiB being the standard page size), the latter must increase that number by the number of pages required by the caller, but without exceeding the maximum limit imposed by the application developer. Since WebAssembly's grow_memory is usually converted to sbrk(2) by implementations, tinyalloc now makes use of this traditional syscall to achieve the desired effect. [1]: https://www.w3.org/TR/2019/REC-wasm-core-1-20191205/#-hrefsyntax-instr-memorymathsfmemorygrow 2025-07-25T22:27:57+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-07-12T15:06:32+00:00 urn:sha1:96d060679a4c34c30a346f1945f88cb8ef45f657 Removing the const qualifier from a const-qualified object and modify it is undefined behaviour. 2025-07-25T22:27:57+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-07-12T15:06:12+00:00 urn:sha1:20c7a57ce7900710787ec04322735eebcb1c5e6e 2025-07-25T22:27:56+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-07-12T15:05:57+00:00 urn:sha1:18194dbd09a81e2993cf03153e1d810aa8abe4cc 2021-10-08T20:40:36+00:00 Karsten Schmidt k@thi.ng 2021-10-08T20:40:36+00:00 urn:sha1:b60fcd7a351dea8a51f3ec95b19fc0d0d2e4dcd9 2020-09-18T00:32:42+00:00 Karsten Schmidt k@postspectacular.com 2020-09-18T00:32:42+00:00 urn:sha1:7273051682ee0b9235bd24b7544f9fe643a023f5 Allow inclusion in CPP projects 2020-09-17T11:32:31+00:00 Ryzee119 wendland@live.com.au 2020-09-17T11:32:31+00:00 urn:sha1:0f1d708a84144cadb2d9462beedc66de1bb48c42 Attempted to use in Arduino, but got linker errors. This resolved the issue. 2020-08-06T10:10:09+00:00 Karsten Schmidt k@postspectacular.com 2020-08-06T10:10:09+00:00 urn:sha1:8241b04999909769bdbd0046c3a2200cfed72367 Fix heap initialization