Tony Wasserka 6681d7dcf9 LookupCache: Split L3 cache into a dedicated interface ...

This data isn't really a cache, since the JIT is directly responsible of
writing its contents. Instead it be considered the source to populate the
L1/L2 caches from.

Furthermore, splitting off this data allows it to be shared across threads
in the future without affecting L1/L2 caches.

2025-06-01 22:42:55 +02:00

..

Config

FEXCore: Move CPUInfo to FEX

2025-04-08 22:54:43 -07:00

Context

IR: drop RegisterAllocationData

2025-05-19 13:42:59 -04:00

Core

LookupCache: Split L3 cache into a dedicated interface

2025-06-01 22:42:55 +02:00

GDBJIT

Whole-tree reformat

2024-04-12 16:26:02 +02:00

IR

RegisterAllocationPass: pair push/pop

2025-05-27 11:33:12 -04:00