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

Chisel 7 Bump Issue due to Default Layers

Open
#84 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
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
scala
Domain
build-system

Research direction

Start with hardfloat/tests/src/FMATester.scala at the ChiselStage invocation around line 61, then inspect how Verilator consumes the generated Verilog. Confirm the behavior introduced by Chisel 7 default layers and choose between specializing them away or using per-module output with an include directory. Done means the generated Verilog is valid and the Verilator invocation can resolve its includes.

Written by the indexing model from the issue text.

Description

FYI: if this project tries to bump to Chisel 7, which now includes default layers, there will be problems with how the FMATester.scala generates Verilog here: https://github.com/ucb-bar/berkeley-hardfloat/blob/26f00d00c3f3f57480065e02bfcfde3d3b41ec51/hardfloat/tests/src/FMATester.scala#L61

With default layers always being there, then doing this may create an invalid single-file Verilog file that has `include directives pointing at directories/files which don't exist.

This can either be fixed by changing the ChiselStage invocation to include -enable-layers arguments that specialize away the default layers or this invocation could be changed to use one-file-per-module output and changing the Verilator invocation to properly setup +incdir pointing at the output directory.

Dominant language
Scala
Stars
393
Forks
110
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 ucb-bar/berkeley-hardfloat

All issues in ucb-bar/berkeley-hardfloat

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.