Centralize function-scope drop handling in gccrs

gccrs now uses a unified try-finally mechanism for function-scope drops, simplifying code generation.

By Lishin July 16, 2026 committed

gccrs centralizes the emission of drop calls for function scopes into a single try-finally cleanup path. This change removes individual drop-emission calls scattered throughout the code and applies the consistent cleanup to constant-item and closure function bodies, simplifying the backend’s drop management.

In Details

The HIRCompileBase::compile_function in gccrs is refactored to use a try-finally structure for managing scope drops, replacing direct calls to emit_current_scope_drop_calls. This pattern is also applied to compile_constant_item and generate_closure_function. The separate CompileDrop::emit_current_scope_drop_calls function is removed.

For Context

gccrs: The GCC backend for the Rust programming language, enabling Rust code to be compiled by GCC.
drop: In Rust, a 'drop' refers to the process of deallocating resources (like memory) when a variable goes out of scope. This is managed by the Drop trait.
try-finally: A control flow structure that executes a 'try' block and guarantees a 'finally' block runs afterward, regardless of whether exceptions occurred. This is used here for reliable resource cleanup.
closure: An anonymous function that can capture variables from its surrounding environment.

Filed Under: rustcompilerbackendcleanup

View Commit →