batch-lift

Batch lifting groups related decompiled functions, such as class methods and call chains, into a single context-rich C++ output to prevent the context loss of lifting functions individually. It builds shared struct definitions and dependency-ordered lift plans.

Lifting export-down subtrees is best handled by grouping them into a batch lift plan that computes dependency ordering. This generates a single cohesive .cpp file containing constants, structs, and functions for easier verification and reuse.

Yes, batch lifting requires DeepExtractIDA analysis DBs to extract function data and scan struct access patterns. These DBs provide the necessary decompiled code context to build shared struct definitions and dependency-ordered lift plans.

Dependency ordering ensures callees are lifted first within the batch. By scanning function data and struct access patterns across the analysis DB, the lift plan orders class methods so that dependencies are resolved before they are called in the final C++ output.

Yes, batch lifting scans struct access patterns across all functions in the batch to build shared struct definitions. It combines these definitions with constants and functions into a single cohesive .cpp file for straightforward verification.

Lifting decompiled functions individually loses context because shared structs and call chain dependencies are isolated. Batch lifting solves this by collecting related functions into one group, building shared definitions, and assembling a cohesive C++ output.