[PATCH] aarch64: ERRAT_NONE is not zero, so test against it
Project / Subsystem
binutils / aarch64
Date
2026-08-06
Proposer
ktkachov@nvidia.com
Source type
public_inbox
Consensus
Proposed
Sentiment
8/10
Technical tradeoffs
- • Ensures erratum workarounds are only applied when explicitly requested, avoiding unnecessary link-time overhead.
All attributes
- project
- binutils
- subsystem
- aarch64
- patch_id
- —
- discussion_id
- 20260806054354.27168-1-ktkachov@nvidia.com
- source_type
- public_inbox
- title
- [PATCH] aarch64: ERRAT_NONE is not zero, so test against it
- headline
- aarch64: ERRAT_NONE is not zero, so test against it
- tldr
- A patch corrects a bug in aarch64 code where a workaround was incorrectly enabled by default due to a faulty comparison with ERRAT_NONE.
- proposer
- ktkachov@nvidia.com
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- 8
- technical_tradeoffs
-
- • Ensures erratum workarounds are only applied when explicitly requested, avoiding unnecessary link-time overhead.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • binutils
- • aarch64
- • errata
- • bfd
- bugzilla_url
- —
- date
- 2026-08-06T00:00:00.000Z
[PATCH] aarch64: ERRAT_NONE is not zero, so test against it
This patch addresses an issue in the aarch64 BFD backend where the fix_erratum_843419 workaround was being incorrectly enabled by default. The problem stems from ERRAT_NONE not being zero, causing a simple boolean test to evaluate as true even when no workaround was explicitly requested. The fix involves changing the comparison to explicitly check against ERRAT_NONE, aligning it with other erratum checks in the file.