Skip to content

build: migrate chisel_binary to bazel bcr rules_chisel#9834

Merged
maliberty merged 1 commit intoThe-OpenROAD-Project:masterfrom
Pinata-Consulting:bazel-orfs-bump-chisel
Mar 19, 2026
Merged

build: migrate chisel_binary to bazel bcr rules_chisel#9834
maliberty merged 1 commit intoThe-OpenROAD-Project:masterfrom
Pinata-Consulting:bazel-orfs-bump-chisel

Conversation

@oharboe
Copy link
Collaborator

@oharboe oharboe commented Mar 19, 2026

The local bazel-orfs moved chisel support from
@bazel-orfs//toolchains/scala:chisel.bzl to the standalone @rules_chisel//chisel:defs.bzl package. Add rules_chisel as a dev dependency, configure the chisel extension toolchain, and update the mock-array BUILD load path accordingly.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request successfully migrates the Chisel build system from @bazel-orfs to @rules_chisel. This involves updating the MODULE.bazel file to include the new rules_chisel dependency and configure its toolchain, as well as updating the BUILD file in test/orfs/mock-array to load chisel_binary from the correct location. The changes are functionally correct for the migration.

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@oharboe oharboe changed the title [DO NOT REVIEW] build: migrate chisel_binary to rules_chisel [DO NOT REVIEW] build: migrate chisel_binary to bazel bcr rules_chisel Mar 19, 2026
@oharboe oharboe force-pushed the bazel-orfs-bump-chisel branch from e279e25 to a39b574 Compare March 19, 2026 15:38
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@oharboe oharboe marked this pull request as ready for review March 19, 2026 21:40
The local bazel-orfs moved chisel support from
@bazel-orfs//toolchains/scala:chisel.bzl to the standalone
@rules_chisel//chisel:defs.bzl package. Add rules_chisel as a
dev dependency, configure the chisel extension toolchain, and
update the mock-array BUILD load path accordingly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
@oharboe oharboe force-pushed the bazel-orfs-bump-chisel branch from a39b574 to 215843a Compare March 19, 2026 21:46
@oharboe oharboe changed the title [DO NOT REVIEW] build: migrate chisel_binary to bazel bcr rules_chisel build: migrate chisel_binary to bazel bcr rules_chisel Mar 19, 2026
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@oharboe
Copy link
Collaborator Author

oharboe commented Mar 19, 2026

/gemini review

@oharboe oharboe requested a review from maliberty March 19, 2026 22:24
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the bazel-orfs commit hash, adds rules_chisel as a bazel dependency, updates the orfs docker image and sha256, and adds chisel toolchain configurations.

@oharboe
Copy link
Collaborator Author

oharboe commented Mar 19, 2026

@maliberty Don't care about pr-head when pr-merge works.

@maliberty maliberty merged commit 201c137 into The-OpenROAD-Project:master Mar 19, 2026
14 of 15 checks passed
@maliberty
Copy link
Member

I don't understand why we need chisel at all - shouldn't that come from bazel-orfs?

@oharboe
Copy link
Collaborator Author

oharboe commented Mar 19, 2026

I don't understand why we need chisel at all - shouldn't that come from bazel-orfs?

The chisel version that we use in mock-array is defined by OpenROAD. mock-array has a chisel version internally that is a developer dependency.

Besides, chisel was only empherally supported by bazel-orfs, now its in bazel bcr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants