Experimental chisel7 support

[jerryz123]

Related PRs / Issues:

Type of change:

• Bug fix
• New feature
• Other enhancement

Impact:

• RTL change
• Software change (RISC-V software)
• Build system change
• Other

Contributor Checklist:

• Did you set main as the base branch?
• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you state the type-of-change/impact?
• Did you delete any extraneous prints/debugging code?
• Did you mark the PR with a changelog: label?
• (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
• (If applicable) Did you add documentation for the feature?
• (If applicable) Did you add a test demonstrating the PR?

• (If applicable) Did you mark the PR as Please Backport?

CI Help:
Add the following labels to modify the CI for a set of features.
Generally, a label added only affect subsequent changes to the PR (i.e. new commits, force pushing, closing/reopening).
See ci:* for full list of labels:

• ci:fpga-deploy - Run FPGA-based E2E testing
• ci:local-fpga-buildbitstream-deploy - Build local FPGA bitstreams for platforms that are released
• ci:disable - Disable CI

[iansseijelly]

OK I guess this is good enough for now, although fragmentation is increasing

[iansseijelly]

oh... how does this work? regardless of useChisel7 or not, wouldn't hf require midas as a dependency?

[jerryz123]

I think this was our hacky way to make everything depend on midas-target-utils in the pre-chisel7 flow

[jerryz123]

@codex review

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

[tianrui-wei]

This currently breaks Boom RTL generation in chisel7, even with chisel version set to 7.0.0, and can be reproduced by running

make verilog USE_CHISEL7=1 CONFIG=MediumBoomV3Config

Specifically, the issue arises from after running the firtool transform, the rob_debug_inst_mem gets transformed into rob_debug_inst_mem_ext in the mems.conf file, but not the model_module_hierarchy.json. I'm not sure whether this is an issue in sfc or firtool. Any ideas?

[tianrui-wei]

Tracking llvm/circt#9012, we should bump the firtool after the fix.