Re: [PATCH v3] x86: Generate PLT32 relocation for ".long foo@PLT - .L4"

Project / Subsystem

binutils / x86

Date

2026-07-29

Proposer

"H.J. Lu" <hjl.tools@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

  • • Ensuring correct PLT resolution for indirect function calls.
  • • Handling specific assembler directives that require PLT32 relocation.
  • • Maintaining compatibility with existing relocation mechanisms.

All attributes

project
binutils
subsystem
x86
patch_id
—
discussion_id
CAMe9rOpksJFKzyKiH4A-2jP97UBC_vNJ_9PQm+uOq8_v5cwjsQ@mail.gmail.com
source_type
public_inbox
title
Re: [PATCH v3] x86: Generate PLT32 relocation for ".long foo@PLT - .L4"
headline
x86: Generate PLT32 relocation for ".long foo@PLT - .L4"
tldr
H.J. Lu confirms the necessity and correctness of generating R_X86_64_PLT32 for specific directives to resolve PC32 relocations against function symbols.
proposer
"H.J. Lu" <hjl.tools@gmail.com>
consensus
Proposed
outcome
proposed
sentiment_score
—
technical_tradeoffs
  • • Ensuring correct PLT resolution for indirect function calls.
  • • Handling specific assembler directives that require PLT32 relocation.
  • • Maintaining compatibility with existing relocation mechanisms.
series_id
—
series_role
standalone
series_parts
[]
tags
  • • binutils
  • • x86
  • • relocation
  • • linker
  • • assembler
bugzilla_url
—
date
2026-07-29T00:00:00.000Z

Re: [PATCH v3] x86: Generate PLT32 relocation for ".long foo@PLT - .L4"

In response to Jan Beulich’s questions, H.J. Lu clarifies that the patch is necessary for generating the R_X86_64_PLT32 relocation for directives like “.long foo@PLT - .L4”. This ensures that PLT entries are used to resolve PC32 relocations against function symbols, addressing a reported gas PR.