Skip to content

Don't handle special case of reductions for scalar inputs and "empty" reduction axes#6322

Open
copybara-service[bot] wants to merge 1 commit intomainfrom
test_882225739
Open

Don't handle special case of reductions for scalar inputs and "empty" reduction axes#6322
copybara-service[bot] wants to merge 1 commit intomainfrom
test_882225739

Conversation

@copybara-service
Copy link

Don't handle special case of reductions for scalar inputs and "empty" reduction axes

TFlite has a wierd thing where it allows specifying that the shape {0} (not {}) means "scalar" or empty. XNNPACK does not have this special case, and I don't think we should support it.

@copybara-service copybara-service bot force-pushed the test_882225739 branch 3 times, most recently from 75ad313 to af7e28c Compare March 13, 2026 23:00
… reduction axes

TFlite has a wierd thing where it allows specifying that the shape `{0}` (not `{}`) means "scalar" or empty. XNNPACK does not have this special case, and I don't think we should support it.

PiperOrigin-RevId: 882225739
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.

1 participant