[jit, exception] use shared mutex to reduce thread contention of cached code blocks in fastmem trap handler #320
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "usesharedmutexinsteadofhardmutex"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ankerl::unordered_dense::map will provide better lookup times, theoretically.
fastmem trap handler usually had mutex contention for non-linkable series of blocks (block linking failures); so just use shared_mutex
Signed-off-by: lizzie lizzie@eden-emu.dev
55335b7f9f
to8e4bbf0d5b
8e4bbf0d5b
to8d64521d7f
8d64521d7f
to9ca5804990
8d64521d7f
to61e56a037d
61e56a037d
tof23a55bb69
f23a55bb69
to170401b3d3
170401b3d3
to440625f8af
440625f8af
to063a240195
063a240195
to7d7f319901
No issues with this on Windows. Did the best to test with the games I had. No regressions or issues found.
7d7f319901
toa6c594c364
a6c594c364
to4c029ad345
4c029ad345
toc8fcafbb2a
c8fcafbb2a
to2e47f4c857
2e47f4c857
to67f5a76f09