Re: RFC: Should -fplugin and -fplugin-arg options be excluded from DW_AT_producer recording?

Project / Subsystem

gcc / gcc/debug

Date

2026-08-16

Proposer

Pietro Monteiro <pietro.gcc@sociotechnical.xyz>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

  • • Excluding plugin paths enhances reproducibility but removes potentially useful information from DW_AT_producer.
  • • Relying on the `NoDWARFRecord` mechanism requires careful maintenance as compiler options evolve.

All attributes

project
gcc
subsystem
gcc/debug
patch_id
—
discussion_id
e7bb6bf1-8d23-458b-8c32-6e6f4d1837fc@app.fastmail.com
source_type
public_inbox
title
Re: RFC: Should -fplugin and -fplugin-arg options be excluded from DW_AT_producer recording?
headline
RFC: Exclude -fplugin options from DW_AT_producer
tldr
Proposes excluding absolute plugin paths from DW_AT_producer debug metadata to improve build reproducibility.
proposer
Pietro Monteiro <pietro.gcc@sociotechnical.xyz>
consensus
Proposed
outcome
proposed
sentiment_score
—
technical_tradeoffs
  • • Excluding plugin paths enhances reproducibility but removes potentially useful information from DW_AT_producer.
  • • Relying on the `NoDWARFRecord` mechanism requires careful maintenance as compiler options evolve.
series_id
—
series_role
standalone
series_parts
[]
tags
  • • debug
  • • reproducibility
  • • compiler
  • • plugins
  • • DWARF
bugzilla_url
—
date
2026-08-16T00:00:00.000Z

Re: RFC: Should -fplugin and -fplugin-arg options be excluded from DW_AT_producer recording?

This RFC proposes excluding GCC’s -fplugin and -fplugin-arg options from being recorded in the DW_AT_producer debug metadata. Currently, absolute paths to plugins can be embedded, potentially compromising build reproducibility. The suggested change uses GCC’s existing NoDWARFRecord mechanism, which has previously been employed for similar reproducibility concerns.