losfair / losfair/Violet

Early branch

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
35
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently branches aren't applied until they are committed. This gives a misprediction penalty of at least 6 cycles.

By adding an "early branch" signal we can allow the branch units to request a branch at the frontend directly, which would hopefully reduce misprediction penalty to 4 cycles.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue names no files or tests. Start by tracing the branch units and frontend to understand where branches are currently applied, then determine how an early branch request would be validated against the stated misprediction-penalty target.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.