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.

Sign up for GitHub

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

Jump to bottom

AIRDependency: Determine whether to add a dependency based on dominance info #875

Merged
merged 6 commits into from
Jan 23, 2025
Merged

AIRDependency: Determine whether to add a dependency based on dominance info #875

merged 6 commits into from
Jan 23, 2025

Conversation

erwei-xilinx
Copy link
Collaborator

... instead of relying on globally declared "op_history" vectors to keep track of op dominance, which is hacky.

@erwei-xilinx erwei-xilinx requested a review from fifield as a code owner January 23, 2025 01:52
@erwei-xilinx erwei-xilinx merged commit a598b31 into Xilinx:main Jan 23, 2025
11 checks passed
@erwei-xilinx erwei-xilinx deleted the air_dependency_use_dominance branch January 23, 2025 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fifield fifield Awaiting requested review from fifield fifield is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@erwei-xilinx