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

[TensorRT EP] Fix wrong input order when generating IndexedSubGraph #22857

Merged
merged 3 commits into from
Dec 2, 2024

Conversation

chilo-ms
Copy link
Contributor

The input order of generated indexedSubGraph needs to be consistent with the input order of original graph.

This PR will also fix the github issue
#22729

@chilo-ms chilo-ms merged commit e234023 into main Dec 2, 2024
91 of 93 checks passed
@chilo-ms chilo-ms deleted the chi/fix_ep_context_model_input_order branch December 2, 2024 09:45
guschmue pushed a commit that referenced this pull request Dec 2, 2024
…22857)

The input order of generated indexedSubGraph needs to be consistent with
the input order of original graph.

This PR will also fix the github issue
#22729
ankitm3k pushed a commit to intel/onnxruntime that referenced this pull request Dec 11, 2024
…icrosoft#22857)

The input order of generated indexedSubGraph needs to be consistent with
the input order of original graph.

This PR will also fix the github issue
microsoft#22729
ankitm3k pushed a commit to intel/onnxruntime that referenced this pull request Dec 11, 2024
…icrosoft#22857)

The input order of generated indexedSubGraph needs to be consistent with
the input order of original graph.

This PR will also fix the github issue
microsoft#22729
tarekziade pushed a commit to tarekziade/onnxruntime that referenced this pull request Jan 10, 2025
…icrosoft#22857)

The input order of generated indexedSubGraph needs to be consistent with
the input order of original graph.

This PR will also fix the github issue
microsoft#22729
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.

2 participants