rodata-lookup-caching: fix grammar
This commit is contained in:
parent
a0ee2169e5
commit
7f0d22e5dc
@ -7,8 +7,8 @@ CSS: /style.css
|
|||||||
While working on our immediate no-state engine, the need for texture lookup optimization arose.
|
While working on our immediate no-state engine, the need for texture lookup optimization arose.
|
||||||
API is designed in a way where every single pushed triangle means resolution of texture by path.
|
API is designed in a way where every single pushed triangle means resolution of texture by path.
|
||||||
|
|
||||||
My insane mind came to such optimization then: detect is given path pointer is in .rodata and if so, -
|
My insane mind came to such optimization then: detect whether given path pointer is in .rodata and if so, -
|
||||||
just lookup by hash of the pointer, not whole varying-size string. Constant time and all that.
|
just lookup by hash of the pointer itself, not whole varying-size string. Constant time and all that.
|
||||||
|
|
||||||
For that I ended up writing a limited ELF parsing routine that expects `/proc/self/exe`.
|
For that I ended up writing a limited ELF parsing routine that expects `/proc/self/exe`.
|
||||||
Virtual address space randomization was tricky until I realized that
|
Virtual address space randomization was tricky until I realized that
|
||||||
|
Loading…
Reference in New Issue
Block a user