Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark return value of .asTypeOf as "deprecated read-only" #4198

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

jackkoenig
Copy link
Contributor

Users will now get a deprecation warning if they connect to the result of .asTypeOf.

Marked for backporting to 6.x so that we can change this in 7.0.

Contributor Checklist

  • Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

  • API deprecation

Desired Merge Strategy

  • Squash

Release Notes

Previously, .asTypeOf would return a Wire. To get the old behavior, wrap the .asTypeOf call in WireInit(...).

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Deprecation Deprecates an API, will be included in release notes label Jun 20, 2024
@jackkoenig jackkoenig added this to the 6.x milestone Jun 20, 2024
Users will now get a deprecation warning if they connect to the result
of .asTypeOf.
Comment on lines +322 to +324
chirrtl should include("wire _zero_WIRE : { foo : UInt<1>, bar : UInt<1>[0]}")
chirrtl should include("connect _zero_WIRE.foo, UInt<1>(0h0)")
chirrtl should include("connect io, _zero_WIRE")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This change to the .fir is unfortunate, I will look into this later (perhaps we need naming to contemplate views).

Copy link
Member

@seldridge seldridge left a comment

Choose a reason for hiding this comment

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

LGTM

@jackkoenig jackkoenig merged commit 00c7a62 into main Jun 20, 2024
15 checks passed
@jackkoenig jackkoenig deleted the astypeof-readonly-deprecate branch June 20, 2024 23:08
@mergify mergify bot added the Backported This PR has been backported label Jun 20, 2024
mergify bot pushed a commit that referenced this pull request Jun 20, 2024
Users will now get a deprecation warning if they connect to the result
of .asTypeOf.

(cherry picked from commit 00c7a62)
chiselbot pushed a commit that referenced this pull request Jun 20, 2024
Users will now get a deprecation warning if they connect to the result
of .asTypeOf.

(cherry picked from commit 00c7a62)

Co-authored-by: Jack Koenig <koenig@sifive.com>
@sequencer
Copy link
Member

This PR introduced bug to T1. Related code snippet:

  val slotControl: Vec[InstructionControlRecord] =
    RegInit(
      VecInit(
        Seq.fill(parameter.chainingSize)(0.U.asTypeOf(new InstructionControlRecord(parameter)))
      )
    )

error message:

Caused by: chisel3.package$ChiselException: Connection between left (Lane.slotControl_?[0]: Wire[InstructionControlRecord]) and source (Lane.slotControl_?: Wire[InstructionControlRecord]) failed @.mask.bits: Locally unclear whether Left or Right (both internal)

@jackkoenig
Copy link
Contributor Author

Thanks for the report, looking into it!

@jackkoenig
Copy link
Contributor Author

This issue is caused by a weird interaction between how VecInit and directionality work. VecInit picks <> if the source is bidirectional1, which then due to the specialized logic to sometimes emit FIRRTL bulk connects, will emit a FIRRTL bulk connect in this case2. This PR broke that because it is conservative and won't issue bulk connections if either side is marked read-only3. That could change, we could still issue the bulk connect, but the real issue is actually #4204. The direction of your InstructionControlRecord is being reported as Bidirectional(Default) even though it isn't bidirectional due to the bug in the linked issue. So I'm going to fix that.

Footnotes

  1. https://github.com/chipsalliance/chisel/blob/00c7a6288386b237be45fe471e67d9b9cc3192a4/core/src/main/scala/chisel3/Aggregate.scala#L646

  2. https://github.com/chipsalliance/chisel/blob/00c7a6288386b237be45fe471e67d9b9cc3192a4/core/src/main/scala/chisel3/internal/BiConnect.scala#L196

  3. https://github.com/chipsalliance/chisel/blob/00c7a6288386b237be45fe471e67d9b9cc3192a4/core/src/main/scala/chisel3/internal/BiConnect.scala#L133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backported This PR has been backported Deprecation Deprecates an API, will be included in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants