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
Weird Regression with 224ee39 (Vec issue) #348
Comments
A few more details (which are technically just interpretations of/elaborations on the stack trace). I'm importing After digging a bit, it looks like
I'm at a loss as to why this is dependent on the number of times that I run the dynamically indexed read method of |
And, I have a rough fix: The file declaring the class for If somebody gets the time, could you fill me in on what's likely going on here? I do realize I've been living precariously on the edge of advised/sane adoption of alpha (now beta!) tools, but I appreciate all the help. |
I was unable to reproduce this with simple types in current chisel3
works fine. |
@seldridge I'm going to close this, please reopen (and help us reproduce it) if it's still a problem |
Bumps [chisel3](https://github.com/freechipsproject/chisel3) from `9f1eae1` to `5a79814`. - [Release notes](https://github.com/freechipsproject/chisel3/releases) - [Commits](9f1eae1...5a79814) --- updated-dependencies: - dependency-name: chisel3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I'm getting a weird regression with 224ee39 (checked via bisect), but I haven't been able to get an MWE that actually trips. I have a
Vec(Seq.fill(n)(Module(new MyMod).io))
and repeated assignment with more than 4 statements causes the reflection to go nuts.The exact structure is the following (from ripping out all the extraneous code of an internal version of the original):
However, since I can't get an equivalent MWE failing in a less cluttered environment, the issue could be related to some interaction with something else...
The text was updated successfully, but these errors were encountered: