Re: [PATCH v2] Write alignment of `.tls` into `_tls_used.Characteristics`
Project / Subsystem
binutils / binutils
Date
2026-10-05
Proposer
Jan Beulich <jbeulich@suse.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Potential performance improvements from tighter alignment vs. risk of breaking existing code.
- • Enforcing stricter interpretation of ABI/file format specifications.
All attributes
- project
- binutils
- subsystem
- binutils
- patch_id
- —
- discussion_id
- 10855e94-ce2e-457a-8cb0-9feae17ecda7@suse.com
- source_type
- public_inbox
- title
- Re: [PATCH v2] Write alignment of `.tls` into `_tls_used.Characteristics`
- headline
- Write alignment of `.tls` into `_tls_used.Characteristics`
- tldr
- Debate continues on whether extremely small alignment values for .tls sections can break existing code and the interpretation of `_tls_used`.
- proposer
- Jan Beulich <jbeulich@suse.com>
- consensus
- Proposed
- outcome
- under_review
- sentiment_score
- —
- technical_tradeoffs
-
- • Potential performance improvements from tighter alignment vs. risk of breaking existing code.
- • Enforcing stricter interpretation of ABI/file format specifications.
- series_id
- —
- series_role
- reply
- series_parts
- []
- tags
-
- • binutils
- • linker
- • tls
- • pe
- • alignment
- bugzilla_url
- —
- date
- 2026-10-05T00:00:00.000Z
Re: [PATCH v2] Write alignment of `.tls` into `_tls_used.Characteristics`
Jan Beulich expresses ongoing concern that very small alignment values for .tls sections might break existing code, despite the proposed patch. The discussion touches upon the potential issues with Microsoft’s CRT and clang/MSVC, and the reservation of the _tls_used identifier. The author of the patch has not yet provided a definitive reference to support the claims about under-alignment issues or the reserved nature of _tls_used.