[GSoC] Rust Drop trait support in gccrs - Status Report 4

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-07-19

Proposer

Janet Chien <lishin1008@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

• Migrating from manual drop call emission to `TRY_FINALLY_EXPR` simplifies code but requires careful mapping of Rust's drop semantics to GCC's internal exception handling.

View thread →

All attributes

project: gcc
subsystem: gcc
patch_id: —
discussion_id: CAHtgQQsDtZD8pJtRSZym-9_p_C56qfceAG3uYJ_s95F9F+Pm+Q@mail.gmail.com
source_type: public_inbox
title: [GSoC] Rust Drop trait support in gccrs - Status Report 4
headline: Rust Drop trait support in gccrs - Status Report 4
tldr: GSoC student reports progress on implementing Rust's Drop trait in GCC, focusing on exception handling.
proposer: Janet Chien <lishin1008@gmail.com>
consensus: Proposed
outcome: proposed
sentiment_score: —
technical_tradeoffs: • Migrating from manual drop call emission to `TRY_FINALLY_EXPR` simplifies code but requires careful mapping of Rust's drop semantics to GCC's internal exception handling.
series_id: —
series_role: standalone
series_parts: []
tags: • gccrs
• rust
• gsoc
• drop-trait
url: https://inbox.sourceware.org/gcc/CAHtgQQsDtZD8pJtRSZym-9_p_C56qfceAG3uYJ_s95F9F+Pm+Q@mail.gmail.com
bugzilla_url: —
date: 2026-07-19T00:00:00.000Z

[GSoC] Rust Drop trait support in gccrs - Status Report 4

This is a status report on a Google Summer of Code project to implement Rust’s Drop trait in gccrs, the Rust frontend for GCC. The primary focus has been on refactoring cleanup mechanisms to use TRY_FINALLY_EXPR instead of manual drop calls, with several patches merged or under review. The project also aims to align the gccrs design with rustc’s approach.