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

[VitisAI] Wrong model path after using std::filesystem::path #21279

Closed
BoarQing opened this issue Jul 8, 2024 · 6 comments
Closed

[VitisAI] Wrong model path after using std::filesystem::path #21279

BoarQing opened this issue Jul 8, 2024 · 6 comments
Labels
ep:VitisAI issues related to Vitis AI execution provider platform:windows issues related to the Windows platform stale issues that have not been addressed in a while; categorized by a bot

Comments

@BoarQing
Copy link
Contributor

BoarQing commented Jul 8, 2024

Describe the issue

after https://github.com/microsoft/onnxruntime/pullafter /20920, the onnxruntime with provider option --use-vitisai can't be compiled.
In addition, It is using the model path instead of path we specified(l(usually an intermediate model during graph transformation for debugging).

We highly recommended that the onnxruntime's CI can be tested with --use-vitisai, at least for compile.

To reproduce

No need to reproduce.

Urgency

No response

Platform

Windows

OS Version

Win 11

ONNX Runtime Installation

Built from Source

ONNX Runtime Version or Commit ID

main

ONNX Runtime API

C++

Architecture

X64

Execution Provider

Vitis AI

Execution Provider Library Version

No response

@github-actions github-actions bot added ep:VitisAI issues related to Vitis AI execution provider platform:windows issues related to the Windows platform labels Jul 8, 2024
@BoarQing
Copy link
Contributor Author

BoarQing commented Jul 8, 2024

@snnn

@BoarQing
Copy link
Contributor Author

BoarQing commented Jul 8, 2024

Sample compile error:
image

@snnn
Copy link
Member

snnn commented Jul 8, 2024

Should have been fixed by #21247

@snnn snnn closed this as completed Jul 8, 2024
@BoarQing
Copy link
Contributor Author

BoarQing commented Jul 9, 2024

Should have been fixed by #21247
No. This only solves the compile issue

@BoarQing
Copy link
Contributor Author

BoarQing commented Jul 9, 2024

Should have been fixed by #21247

#21293
Could you review this PR that address the issue mentioned on the title.

@snnn snnn reopened this Jul 9, 2024
Copy link
Contributor

github-actions bot commented Aug 9, 2024

This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details.

@github-actions github-actions bot added the stale issues that have not been addressed in a while; categorized by a bot label Aug 9, 2024
@BoarQing BoarQing closed this as completed Nov 5, 2024
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 platform:windows issues related to the Windows platform stale issues that have not been addressed in a while; categorized by a bot
Projects
None yet
Development

No branches or pull requests

2 participants