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

Non deterministic virtual warning #711

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

blueluna
Copy link
Contributor

Adding a warning message when there is a non-deterministic selection of a virtual core during setup.

@olofk
Copy link
Owner

olofk commented Dec 18, 2024

@a-will @HU90m Will this solve the non-determinism for virtual cores in OpenTitan? (cc @Razer6)

@olofk
Copy link
Owner

olofk commented Dec 18, 2024

@blueluna Lint check fails. Make sure to run pre-commit install in the repo root so you get lint checks on every commit

@blueluna blueluna force-pushed the non-deterministic-virtual-warning branch 2 times, most recently from b24d533 to e52edbe Compare December 18, 2024 18:21
@a-will
Copy link
Contributor

a-will commented Dec 18, 2024

@a-will @HU90m Will this solve the non-determinism for virtual cores in OpenTitan? (cc @Razer6)

It's a useful warning, at least! So build issues can be more readily explained in case someone forgot to add the implementing core to a core file.

If the user did specify which virtual core should be used, then #668 ensures that it actually would get used.

The last interesting bit might be not requiring the VLNVs to be placed in a core file (i.e. a mechanism to choose the cores from a command line option, adding to "requirements" alongside the tree generated by the system core). I just had to update about 200 core files to add implementing core specs for lint targets in OpenTitan, where the feature might have reduced that down to a single flow config file. 😅

@blueluna blueluna force-pushed the non-deterministic-virtual-warning branch from e52edbe to 7a1e1f4 Compare December 19, 2024 11:04
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