| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Replaced all occurrences of `rb_get_righter` with `rb_get_rightmost` and
`rb_get_lefter` with `rb_get_leftmost` for improved semantic clarity.
Also updated related function declarations, definitions, and usage
across:
- rbtree.c
- rbtree.h
- custommem.c
- dynablock.c
- env.c
- box64context.c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove outdated information
- Document the seven red-black trees that Box64 currently uses:
1. memprot
2. mapallmem
3. blockstree
4. db_sizes
5. envmap
6. rbt_dynmem
7. volatileRanges
- Clarify each tree's role
The original intention was to help future contributors who want
to propose a faster lookup mechanism to replace rbtrees in the
future, as understanding the current usage patterns is a
necessary first step.
|
| | |
|
| | |
|
| |
|
|
| |
setting
|
| |
|
|
| |
FindDynablockFromNativeAddress function
|
| |
|
|
|
|
| |
Enhanced the rbtree.h header with detailed documentation comments for
each function.
This comment aims to clarify the role of the red-black tree in memory
management and how these functions interact with and manage memory.
|
| |
|
|
|
| |
Red-black tree operations now consistently use the 'rbtree_' prefix, and
internal functions remain unexposed. Tested on RV64GC, resulting in a
498-byte reduction in the .text section size.
|
| | |
|
| | |
|
| | |
|
|
|
* [MEMORY] Switched from a sparse array to an RB tree
* [RBTREE] Fixed the Android build
|