Skip to content

[VitisAI] Upstream changes from win-ort #25448

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

Merged
merged 2 commits into from
Jul 19, 2025
Merged

Conversation

nieubank
Copy link
Contributor

Implement VitisAI execution provider factory and dynamic library location retrieval from win-ort-main

Implement VitisAI execution provider factory and dynamic library location retrieval from win-ort-main
@snnn
Copy link
Member

snnn commented Jul 18, 2025

/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows x64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline

Copy link

Azure Pipelines successfully started running 5 pipeline(s).

mschofie
mschofie previously approved these changes Jul 18, 2025
@jywu-msft jywu-msft added the ep:VitisAI issues related to Vitis AI execution provider label Jul 18, 2025
@nieubank nieubank merged commit 7f193b1 into main Jul 19, 2025
90 of 91 checks passed
@nieubank nieubank deleted the nieubank/vitisai_factory branch July 19, 2025 01:54
@jywu-msft
Copy link
Member

fyi this probably needs to be updated @nieubank because of #25456
similar to the merge conflict I resolved in #25407

@nieubank
Copy link
Contributor Author

#25456

Just put #25475 up for PR

@snnn
Copy link
Member

snnn commented Jul 25, 2025

Hi there! We haven't cut the release branch for this version yet, so I'm removing the release:1.23.0 label for now to keep things tidy. Thanks so much for your contribution! We'll make sure this gets included when the release is prepared. 🤖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ep:VitisAI issues related to Vitis AI execution provider
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants