Chisel 6.4.0 and new hierarchy API?

[Øyvind Harboe]

Should https://www.chisel-lang.org/docs/cookbooks/hierarchy work with Chisel 6.4.0?

[Øyvind Harboe]

Add -Ymacro-annotations to build.sbt...

[Øyvind Harboe]

Created a quick pull request, but my CLA isn't in order(looking into that... but could take a while...).

https://github.com/chipsalliance/chisel/pull/4245/commits/39ba1d54f5d8fde6c720c3c2c1c66eced5bcc295

[Øyvind Harboe]

Followup question. After discovering -Ymacro-annotations, I'm starting to run into problems with BoringUtils.

I'm wondering if BoringUtils and the new hierarchy API is not going to work together because I the hierarchy API is supposed to lock down the module so that it doesn't have to be de-duplicated and the BoringUtils API is trying to modify the module definition to inject new input/output ports to bore down to signals.

Thoughts?

On Friday, July 5, 2024 at 11:47:57 AM UTC+2 Øyvind Harboe wrote:

[Øyvind Harboe]

My PEBCAK.

Seems to work, I think I was having problems with some files not being rebuilt in vscode/bloop, etc.

It does seem like if I start with the Hierarchy API at some point in my modules, then I have to use it all the way down to the modules that I'm using BoringUtils into because everything is not public by default anymore.

[Øyvind Harboe]

On Sunday, July 7, 2024 at 9:12:33 AM UTC+2 Øyvind Harboe wrote:

Followup question. After discovering -Ymacro-annotations, I'm starting to run into problems with BoringUtils.

I'm wondering if BoringUtils and the new hierarchy API is not going to work together because I the hierarchy API is supposed to lock down the module so that it doesn't have to be de-duplicated and the BoringUtils API is trying to modify the module definition to inject new input/output ports to bore down to signals.

The computer said no...

"Cannot bore across a Definition/Instance boundary:"