| .. |
|
tlsf
|
88a5817134
Fix tlsf block adjustment
|
11 mesi fa |
|
virtual
|
539e9bd2e3
Merge pull request #4836 from laytan/fix-wrong-out-of-memory
|
10 mesi fa |
|
alloc.odin
|
70ddb74e40
Add `mem.make_over_aligned`
|
9 mesi fa |
|
allocators.odin
|
1cf7a56ba7
General clean up of code
|
1 anno fa |
|
doc.odin
|
88f423a38b
Update doc.odin
|
10 mesi fa |
|
mem.odin
|
70ddb74e40
Add `mem.make_over_aligned`
|
9 mesi fa |
|
mutex_allocator.odin
|
1dd9b8560d
build mutex allocator code on freestanding wasm
|
1 anno fa |
|
raw.odin
|
016d1a84d4
[mem]: Document mutex, rollback stack and tracking allocators
|
1 anno fa |
|
rollback_stack_allocator.odin
|
466e29bb38
[mem]: Rollback allocator API consistency
|
1 anno fa |
|
tracking_allocator.odin
|
e5f32e1455
Makes tracking allocator default to crashing on a bad free instead of add to bad_free_array. The bad_free_array remains to not break old code. The new default behavior is implemented in a callback that you can override, there's a second provided callback that provides the old behavior where an element was added to bad_free_array. Rationale: Many people are just checking the allocation_map, but don't check the bad free array. Several examples throughout core that use tracking allocator don't check bad_free_array either, so people have been taught not to check it.
|
1 anno fa |
gingerBill
70ddb74e40
Add `mem.make_over_aligned`