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

Remove -forceAll from ECP5 and MachXO2 Diamond build scripts #609

Merged
merged 1 commit into from Apr 12, 2021
Merged

Remove -forceAll from ECP5 and MachXO2 Diamond build scripts #609

merged 1 commit into from Apr 12, 2021

Conversation

adamgreig
Copy link
Contributor

Closes #604, cc @cr1901.

@codecov
Copy link

codecov bot commented Apr 12, 2021

Codecov Report

Merging #609 (58cfd66) into master (c84d4af) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #609   +/-   ##
=======================================
  Coverage   81.50%   81.50%           
=======================================
  Files          49       49           
  Lines        6461     6461           
  Branches     1287     1287           
=======================================
  Hits         5266     5266           
  Misses       1007     1007           
  Partials      188      188           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c84d4af...58cfd66. Read the comment docs.

@whitequark whitequark merged commit d824795 into amaranth-lang:master Apr 12, 2021
@whitequark
Copy link
Member

Thanks @adamgreig and @cr1901!

@adamgreig adamgreig deleted the no-force-all branch April 12, 2021 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

In ECP5 and MachXO2 backends, is the -forceAll option necessary?
2 participants