webnn: work around ORT expand for 0-D input to 0-D output#59062
Draft
chromium-wpt-export-bot wants to merge 1 commit intomasterfrom
Draft
webnn: work around ORT expand for 0-D input to 0-D output#59062chromium-wpt-export-bot wants to merge 1 commit intomasterfrom
chromium-wpt-export-bot wants to merge 1 commit intomasterfrom
Conversation
Expanding a 0-D input to a 0-D output causes an access violation in a certain ORT EP. Work around this by using an identity node instead, since the operation is a no-op. Bug: 500394293 Change-Id: Ic5ede18f6760e644bf92a8da250fc71af2e2cdcb Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expanding a 0-D input to a 0-D output causes an access violation in a
certain ORT EP. Work around this by using an identity node instead,
since the operation is a no-op.
Bug: 500394293
Change-Id: Ic5ede18f6760e644bf92a8da250fc71af2e2cdcb
Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/7738338
WPT-Export-Revision: eea601c58e084943adc2a23bdef764592b109ae9