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

Integrate v0.6.0 into Cheshire. #41

Closed
wants to merge 2 commits into from
Closed

Integrate v0.6.0 into Cheshire. #41

wants to merge 2 commits into from

Conversation

yvantor
Copy link

@yvantor yvantor commented Apr 10, 2024

No description provided.

github-ci and others added 2 commits March 11, 2024 13:06
@yvantor yvantor marked this pull request as draft April 10, 2024 16:59
@thommythomaso
Copy link
Collaborator

Can you please comment on what this PR fixes? Can you also make sure that no generated files are checked in?

@yvantor
Copy link
Author

yvantor commented Apr 10, 2024

It looks that when you generate the dependencies with the -t rtl flag, Qestasim complains because it does not find the idma_inst64_snitch_pkg (which indeed does not appear in the compile script that Bender generates). Our first guess was the missing space in the list of declared targets that should add the file to the dependencies. So far, adding that space worked.

@thommythomaso
Copy link
Collaborator

I am unsure what the whitespace changes, but the target should only be active if rtl and snitch_cluster are present. What is wrong here is that you need a stub instruction encoding for the thing to compile. I would, in your case, add the snitch_cluster target for now.

@yvantor
Copy link
Author

yvantor commented Apr 10, 2024

@chaoqun-liang

@chaoqun-liang
Copy link
Contributor

I am unsure what the whitespace changes, but the target should only be active if rtl and snitch_cluster are present. What is wrong here is that you need a stub instruction encoding for the thing to compile. I would, in your case, add the snitch_cluster target for now.

Yes, I would go with snitch_cluster for now as we already managed to get it to work this way eariler today. I can also confirm the space in between does not make a difference in this case.

@thommythomaso
Copy link
Collaborator

I would appreciate it if you could create an issue to keep track of this. Closed.

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.

3 participants