Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[proposal] __ARM_FEATURE_DIT

Open
  • Is something wrong?
#463 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
compilers

Research direction

The issue names no file or test; start by locating existing _ARM_FEATURE* definitions and references to FEAT_DIT in the ACLE sources. Compare how static architectural features are exposed, then determine the appropriate macro behavior and validation needed so applications can identify DIT availability.

Written by the indexing model from the issue text.

Description

There is seemingly no __ARM_FEATURE_* flag corresponding to FEAT_DIT. Maybe one could be added? That seems particularly useful here, as it allows an application to skip the non-DIT fallback paths (and thus avoid risk of speculation errors across them!) in a binary that knows DIT is statically available.

Dominant language
Python
Stars
129
Forks
77
Avg merge
8d 12h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ARM-software/acle

All issues in ARM-software/acle

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.