Barinzaya 7819797a03 Split mem.make_map to match the runtime procs. ...

The existing `mem.make_map` passes a capacity, but the builtin
`make_map` no longer takes a capacity--it was separated to
`make_map_cap` to allow for making a map without an allocation (#4340).

`core:mem` was not updated to reflect this, so any usage of `mem.make`
to make a map will currently result in a compile error.

2025-03-22 11:03:04 -04:00

..

tlsf

Fix tlsf block adjustment

2025-02-10 13:01:16 +11:00

virtual

Merge pull request #4836 from laytan/fix-wrong-out-of-memory

2025-03-20 17:20:26 +00:00

alloc.odin

Split mem.make_map to match the runtime procs.

2025-03-22 11:03:04 -04:00

allocators.odin

General clean up of code

2025-01-01 15:13:46 +00:00

doc.odin

Update doc.odin

2025-02-26 03:04:54 -06:00

mem.odin

General clean up of code

2025-01-01 15:13:46 +00:00

mutex_allocator.odin

build mutex allocator code on freestanding wasm

2024-10-14 16:11:25 +02:00

raw.odin

[mem]: Document mutex, rollback stack and tracking allocators

2024-09-14 10:46:35 +11:00

rollback_stack_allocator.odin

[mem]: Rollback allocator API consistency

2024-09-14 13:15:02 +11:00

tracking_allocator.odin

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.

2024-12-21 15:49:48 +01:00