rizinorg/cutter

[FR] Decompiler caching

Open

#3,178 opened on May 10, 2023

View on GitHub
 (2 comments) (1 reaction) (0 assignees)C++ (14,852 stars) (1,123 forks)batch import
DecompilerHelp Wanted

Description

Is your feature request related to a problem? Please describe.

When going back and forth through history in the decompiler widget, the functions are decompiled again and again, causing some lag.

Describe the solution you'd like

It would be nice to have some sort of caching to speed things up.

Describe alternatives you've considered

Additional context

Contributor guide

Tech stack
cpp
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of C++Understanding of decompiler internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current decompiler widget (src/widgets/DecompilerWidget.cpp) and the rizin decompiler API to identify where decompilation is triggered. Consider implementing a simple cache (e.g., LRU cache) to store decompiled output for recently visited history states. Ensure cache invalidation when code or configuration changes. Look at existing similar caching patterns in the codebase for reference.
[FR] Decompiler caching · rizinorg/cutter#3178 | Good First Issue