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

Clash should consider primitives when caching compilation results #332

Closed
leonschoorl opened this issue Jul 24, 2018 · 1 comment
Closed
Assignees
Labels
bug patch-provided Patch provided in comments: needs review, merge, etc.

Comments

@leonschoorl
Copy link
Member

When you change a primitive in a .json file and rerun clash, it will seem to ignore these changes.

Only when you also change your .hs file or recompile with the -fclash-nocache flag will your primitive changes end up in the output.

@martijnbastiaan martijnbastiaan self-assigned this Oct 5, 2018
@martijnbastiaan
Copy link
Member

Additionally, account for hash of own Clash binary (if applicable) if possible

@martijnbastiaan martijnbastiaan added the patch-provided Patch provided in comments: needs review, merge, etc. label Oct 8, 2018
leonschoorl pushed a commit that referenced this issue Jul 31, 2023
Renamed the options for the `--hardware-targets` flag to: `OneAny`,
`Specific {FPGA indices}` and `All`. Defaults to `OneAny`.

Some examples:

--hardware-targets=OneAny -> First FPGA Vivado can find
--hardware-targets=All -> All FPGAs in the demo rack
--hardware-targets="Specific [1,2,5]" -> Only FPGAs 1, 2 and 5 in demo rack
--hardware-targets="Specific [-1,-2]" -> Only the last 2 FPGAs in the demo rack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug patch-provided Patch provided in comments: needs review, merge, etc.
Projects
None yet
Development

No branches or pull requests

2 participants