Re: [PATCH] x86: support -Ofast
Project / Subsystem
binutils / x86
Date
2026-09-01
Proposer
Jan Beulich <jbeulich@suse.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Balancing aggressive optimization with strict standards compliance.
- • Defining the scope of the -Ofast flag in the assembler.
- • Potential impact on program correctness due to relaxed constraints.
All attributes
- project
- binutils
- subsystem
- x86
- patch_id
- —
- discussion_id
- 68f081b9-2332-4c98-b2ae-3baf1f404f6f@suse.com
- source_type
- public_inbox
- title
- Re: [PATCH] x86: support -Ofast
- headline
- x86: support -Ofast
- tldr
- Discussion on the implications of adding -Ofast support to binutils, particularly regarding its relaxation of strict commutativity and NaN handling.
- proposer
- Jan Beulich <jbeulich@suse.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Balancing aggressive optimization with strict standards compliance.
- • Defining the scope of the -Ofast flag in the assembler.
- • Potential impact on program correctness due to relaxed constraints.
- series_id
- —
- series_role
- reply
- series_parts
- []
- tags
-
- • binutils
- • gas
- • x86
- • optimization
- • floating-point
- bugzilla_url
- —
- date
- 2026-09-01T00:00:00.000Z
Re: [PATCH] x86: support -Ofast
Jan Beulich discusses the implications of adding -Ofast support to binutils, relating it to GCC’s -Ofast option. The conversation touches on how -Ofast relaxes constraints on instruction commutativity, especially concerning NaN handling in floating-point operations. It also explores whether this option should also control optimizations for NOP-like instructions, like the XCHG to MOV transformation.