Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IFRT] Use AttributeMap wherever applicable in IFRT #13930

Merged
merged 1 commit into from
Jun 29, 2024

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Jun 18, 2024

[IFRT] Use AttributeMap wherever applicable in IFRT

This change uses xla::ifrt::AttributeMap in IFRT Client, Device, and
Topology attributes. It adds utility functions to convert from/to a map of
PjRtValueType that is used in PjRt and was used in these IFRT classes.

IFRT Proxy also uses a native serialization of xla::ifrt::AttributeMap in
Version 4 with an added compatibility for previously supported protocol
versions (the minimum version does not change).

@copybara-service copybara-service bot force-pushed the test_644184301 branch 18 times, most recently from da44842 to 60ef757 Compare June 25, 2024 17:33
@copybara-service copybara-service bot force-pushed the test_644184301 branch 7 times, most recently from b66d015 to c5a9030 Compare June 28, 2024 23:47
This change uses `xla::ifrt::AttributeMap` in IFRT `Client`, `Device`, and
`Topology` attributes. It adds utility functions to convert from/to a map of
`PjRtValueType` that is used in PjRt and was used in these IFRT classes.

IFRT Proxy also uses a native serialization of `xla::ifrt::AttributeMap` in
Version 4 with an added compatibility for previously supported protocol
versions (the minimum version does not change).

PiperOrigin-RevId: 647834051
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