Re: : [RFC PATCH] LoongArch: Use local anchors for relocatable section symbols
Project / Subsystem
binutils / bfd
Date
2026-09-19
Proposer
Gopi Kumar Bulusu <gopi@sankhya.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
6/10
Technical tradeoffs
- • Ensuring the correct handling of section offsets and their interaction with relocations under LoongArch's relaxation constraints.
- • Potential impact on incremental linking and assembler behavior when input and output sections differ.
All attributes
- project
- binutils
- subsystem
- bfd
- patch_id
- —
- discussion_id
- mailman.4.1789819201.2699126.binutils@sourceware.org
- source_type
- public_inbox
- title
- Re: : [RFC PATCH] LoongArch: Use local anchors for relocatable section symbols
- headline
- LoongArch: Use local anchors for relocatable section symbols
- tldr
- Gopi Kumar Bulusu questions whether linker defects map section start to section offset and asks about desired behavior.
- proposer
- Gopi Kumar Bulusu <gopi@sankhya.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- 6
- technical_tradeoffs
-
- • Ensuring the correct handling of section offsets and their interaction with relocations under LoongArch's relaxation constraints.
- • Potential impact on incremental linking and assembler behavior when input and output sections differ.
- series_id
- —
- series_role
- reply
- series_parts
- []
- tags
-
- • linker
- • loongarch
- • relocation
- • optimization
- • rfc
- bugzilla_url
- —
- date
- 2026-09-19T00:00:00.000Z
Re: : [RFC PATCH] LoongArch: Use local anchors for relocatable section symbols
Gopi Kumar Bulusu responds to an RFC patch regarding LoongArch local anchors, questioning the impact of input vs. output section differences on the assembler and incremental linking. He suggests examining the documented behavior for section access and understanding if the current mapping of section start to section offset is by design or a linker defect.