qualcomm/eld

Resolve FIXMEs: cosmetic / speculative / near-dead markers

Open

#1,505 opened on Jul 16, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)C++ (73 forks)auto 404
good first issuerefactor

Repository metrics

Stars
 (254 stars)
PR merge metrics
 (Avg merge 3d 18h) (84 merged PRs in 30d)

Description

Low impact. Several are "verify then maybe delete"; confirm no refs first.

  • include/eld/Support/INIReader.h:29 — "make this private"
  • include/eld/Script/OutputSectData.h:55 — "Ideally, it should be private."
  • include/eld/Input/BitcodeFile.h:70 — "Used by BitcodeReader, may not be needed."
  • lib/Core/Module.cpp:340 — "Test if it's needed at all."
  • lib/Diagnostics/DiagnosticEngine.cpp:214 — "currently there are fewer diagnostic..."
  • include/eld/Input/InputTree.h:86 — "Convert to std::optional"
  • lib/Config/LinkerConfig.cpp:64 — "Use DIAG here."
  • lib/Support/INIReader.cpp:25 — "Check for errors."
  • lib/LinkerWrapper/DWARF.cpp:25 — bare "Remove"
  • lib/Target/X86/x86_64Info.cpp:56 — bare // FIXME
  • lib/Target/AArch64/AArch64LDBackend.h:180 — bare /// FIXME:
  • include/eld/PluginAPI/PluginADT.h:783 — bare // TODO:
  • include/eld/PluginAPI/PluginADT.h:1252 — bare /// TODO
  • lib/Target/Template/TemplateInfo.cpp:24 — "Add proper code."
  • lib/Plugin/PluginActivityLog.cpp:110 — "This needs to be completed."

Contributor guide

Research direction
Inspect each FIXME marker in the specified files. For each, understand the surrounding code and decide whether to implement the suggested change (e.g., make private, remove, convert to optional) or delete the marker if no longer relevant.
Tech stack
cpp
Domain
backendtooling
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70