[IFRT] Add custom_options in ifrt::ExecuteOptions
#20103
Merged
Conversation
This file contains 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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_702507071
branch
5 times, most recently
from
128ce6b
to
60bc2f3
Compare
The users can provide any runtime-specific execution options at `ifrt::LoadedExecutable::Execute()` using `ifrt::ExecuteOptions::custom_options`. These options are intended to convey small per-execution metadata that are to be used by implementation internals with little to (ideally) no interaction with IFRT API semantics. Example use cases are propagating a profiling key, which currently goes out of scope of IFRT APIs. PiperOrigin-RevId: 702546163
copybara-service
bot
force-pushed
the
test_702507071
branch
from
60bc2f3
to
5ad6651
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[IFRT] Add
custom_optionsinifrt::ExecuteOptionsThe users can provide any runtime-specific execution options at
ifrt::LoadedExecutable::Execute()usingifrt::ExecuteOptions::custom_options. These options are intended to conveysmall per-execution metadata that are to be used by implementation internals
with little to (ideally) no interaction with IFRT API semantics. Example use
cases are propagating a profiling key, which currently goes out of scope of
IFRT APIs.