Closed pavel-kirienko closed 2 years ago
The README should be changed accordingly, currently it says
In the case of concurrent environments, also pass pointers to the synchronization locking/unlocking functions -- they will be invoked by the library to facilitate atomic transactions. Alternatively, some applications (where possible) might benefit from using a separate heap per thread to avoid the synchronization overhead and reduce contention.
@jrahlf thanks! Fixed in #10
Remove critical section enter/leave hooks:
https://github.com/pavel-kirienko/o1heap/blob/bd9327732b43ec84d5e44b90f343157ae3240d75/o1heap/o1heap.h#L98-L99
Equivalent behaviors can be implemented by wrapping library calls in custom user code instead.