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

Don't write out of bounds [Fixes #9] #10

Merged
merged 2 commits into from
Jan 2, 2022
Merged

Don't write out of bounds [Fixes #9] #10

merged 2 commits into from
Jan 2, 2022

Conversation

definelicht
Copy link
Contributor

I'm not sure if this will negatively impact performance due to the branch. An alternative solution would be to have dynamically sized loop bounds depending on the tile, which could also negatively impact performance 🤔

@definelicht definelicht changed the title Don't write out of bounds Don't write out of bounds [Fixes #9] Jan 1, 2022
@definelicht definelicht linked an issue Jan 1, 2022 that may be closed by this pull request
@ChrisPattison
Copy link
Collaborator

I would like to review and test this but unfortunately Vitis is broken because it is 2022

@ChrisPattison
Copy link
Collaborator

ChrisPattison commented Jan 2, 2022

I added a verification script that runs through a bunch of different combinations. It passes in the simulation, so I'm good to merge this. We can check for perf regressions after the Xilinx tools get patched

@definelicht definelicht merged commit 0ce6492 into main Jan 2, 2022
@definelicht definelicht deleted the write-oob branch January 2, 2022 13:35
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.

TestHardware failing
2 participants