RE: Remove double-int.

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-09-07

Proposer

Kael Andrew Franco <kaelfandrew@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

• Simplifies build process by removing a component.
• Reduces memory allocation overhead by using heap-less wide integers.
• Requires updating multiple call sites across the compiler.

View thread →

All attributes

project: gcc
subsystem: gcc
patch_id: —
discussion_id: CACAb0qf3QfLDrJR8G_JaYjH=Uhaw1Oqv75KCHxAbZKmjQ6PLiQ@mail.gmail.com
source_type: public_inbox
title: RE: Remove double-int.
headline: Remove double-int.
tldr: Proposes removing the double-int implementation in favor of wide-int.h's fixed_wide_int.
proposer: Kael Andrew Franco <kaelfandrew@gmail.com>
consensus: Proposed
outcome: proposed
sentiment_score: —
technical_tradeoffs: • Simplifies build process by removing a component.
• Reduces memory allocation overhead by using heap-less wide integers.
• Requires updating multiple call sites across the compiler.
series_id: —
series_role: standalone
series_parts: []
tags: • gcc
• internal
• optimization
• cleanup
url: https://inbox.sourceware.org/gcc/CACAb0qf3QfLDrJR8G_JaYjH=Uhaw1Oqv75KCHxAbZKmjQ6PLiQ@mail.gmail.com
bugzilla_url: —
date: 2026-09-07T00:00:00.000Z

RE: Remove double-int.

This RFC proposes to remove the double-int component from GCC. The author argues that wide_int.h’s fixed_wide_int offers similar functionality without heap usage, simplifying parts of the build process and helping with a specific bug (PR126622). The change would involve removing double-int.{cc,h} and updating various other GCC components that currently depend on it.