- User Since
- Mar 30 2020, 11:59 AM (34 w, 6 d)
Oct 22 2020
We are still waiting for discussion on where to put this cache eviction / memory management functionality to better serve existing user via different API layers. While we try to make progress on that, it'll be great if we expose the minimum interface change so that we could reduce the our memory footprint by implementing cache eviction out of LLVM source tree. So, I extracted the minimum changes and sent out https://reviews.llvm.org/D90006 for review. PTAL. Thank you.
Jun 10 2020
FYI, I haven't abandoned this patch. I have been waiting for more opinions including dblaikie@'s.
May 19 2020
Sorry I mistakenly dropped the CMakeLists.txt files in the previous patch. Added them.
Reflected the discussion we've had so far. Made minimum change to the lower level API (DWARFContext, DWARFDebugLine, and DWARFUnit) to make it possible for the high level API and symbolization tool to implement caching. Added a higher level API (DWARFCachedDIContext) that implements DIContext with LRU caching so that llvm-symbolizer could benefit from the caching without code change. It is also a step toward decoupling DWARFContext from DIContext in the future which would be desirable for other use of DWARFContext (e.g. LLDB). Finally, added a unit test for the LRU logic.
May 13 2020
May 12 2020
May 7 2020
May 5 2020
This is a friendly ping. Could you please let me know which direction we should go? Thank you.