Add Span<const Kernel> overload to get_op_function_from_registry

[JacobSzwejbka]

Summary: Expose logic for just scanning a passed in KernelRegistry.

Differential Revision: D98079809

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19519

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Run pull jobs on OSDC in pull requests shadow mode

❌ 6 New Failures, 1 Unrelated Failure

As of commit e093a41 with merge base 9e36d62 ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner (gh)
  >>> Lint for runtime/kernel/test/operator_registry_test.cpp:
• pull / unittest / linux / linux-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1
• pull / unittest / macos / macos-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1
• pull / unittest / windows / windows-job (gh)
  exir/emit/test/test_emit.py::TestEmit::test_delegate_deduplicate
• pull / unittest-editable / linux / linux-job (gh)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• pull / unittest-editable / macos / macos-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@JacobSzwejbka has exported this pull request. If you are a Meta employee, you can view the originating Diff in D98079809.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.