Re: How to add 256 byte sized opaque mode in gcc
Project / Subsystem
gcc / gcc
Date
2026-08-19
Proposer
Avinash Jayakar <avinashd@linux.ibm.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
8/10
Technical tradeoffs
- • Balancing the memory efficiency of a dynamically sized array against the potential overhead of calculating the size at compile time.
- • Ensuring the dynamic sizing logic correctly handles all relevant machine modes without introducing new bugs or performance regressions.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- 20260818101621.162052-1-avinashd@linux.ibm.com
- source_type
- public_inbox
- title
- Re: How to add 256 byte sized opaque mode in gcc
- headline
- How to add 256 byte sized opaque mode in gcc
- tldr
- Avinash Jayakar proposes a patch to dynamically size the mode_unit_size array in GCC based on machine modes, addressing concerns about compile times.
- proposer
- Avinash Jayakar <avinashd@linux.ibm.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- 8
- technical_tradeoffs
-
- • Balancing the memory efficiency of a dynamically sized array against the potential overhead of calculating the size at compile time.
- • Ensuring the dynamic sizing logic correctly handles all relevant machine modes without introducing new bugs or performance regressions.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • optimization
- • machine modes
- • powerpc
- • performance
- • patch
- bugzilla_url
- —
- date
- 2026-08-19T00:00:00.000Z
Re: How to add 256 byte sized opaque mode in gcc
Avinash Jayakar has submitted a patch that dynamically sizes the mode_unit_size array based on the maximum bytesize declared in machine modes, following suggestions from Jakub Jelinek and Richard Biener. This addresses concerns that the change might increase compile times, particularly for powerpc64le. The patch also incorporates style suggestions regarding brace usage.