[5/N] Add get_option/set_option APIs

[cccclai]

Stack from ghstack (oldest at bottom):

• -> [5/N] Add get_option/set_option APIs #11758
• [4/N] Add backend options map #11462
• [3/N] Add get_option/set_option function in backend interface #11391
• [2/N] Add option context #11390
• [1/N] Add BackendOptions class #11389

Expose the API to set/get backend option. We can either pass in {backend_name, backend options} or {backend options map}

Differential Revision: D76825663

Differential Revision: D76825663

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 2 Unrelated Failures

As of commit cfb760b with merge base 608a745 ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for runtime/backend/options_map.h:
• pull / unittest-buck / macos / macos-job (gh)
  runtime/backend/test/backend_options_map_test.cpp:294:30: error: no viable conversion from 'Span<const BackendOption>' to 'Span<BackendOption>'

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-custom-ops-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / unittest-buck / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[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.

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[kimishpatel]

Suggested change

	Error get_option(
	Error get_options(

[kimishpatel]

I dont think we need this. If users want something like that, they can implement it or we wait to see if users want options like that and introduce it later.

[cccclai]

Do you mean get_option function or the get_option with backend option map?

[kimishpatel]

with backend options map, is what i meant

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D76825663

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[meta-cla]

Hi @cccclai!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!