OSSForks/tensorflow
1
0
Fork 0
mirror of https://github.com/zebrajr/tensorflow.git synced 2025-12-06 12:20:11 +01:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

[xla] Update documentation to use xla::Future

Browse Source 
PiperOrigin-RevId: 825222421
This commit is contained in:
Eugene Zhulenev 2025-10-28 15:08:21 -07:00 committed by TensorFlower Gardener
parent 24abec31c7
commit 1d829c0f02
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
third_party/xla/docs/pjrt/cpp_api_overview.md vendored
View File

@ -80,7 +80,7 @@ For communicating with frameworks, buffers know how to convert to and from an
absl::StatusOr<std::unique_ptr<PjRtBuffer>> BufferFromHostBuffer(...) {...}
// Buffer to Literal
xla::PjRtFuture<> ToLiteral(xla::MutableLiteralBase* literal) override {...}
xla::Future<> ToLiteral(xla::MutableLiteralBase* literal) override {...}
```
APIs for creating a buffer have [Buffer Semantics](https://github.com/openxla/xla/blob/3e448cf9e86775a37ec5f7d3c69dfb20e0c760df/xla/pjrt/pjrt_client.h#L858)
@ -138,7 +138,7 @@ reference. These buffers are then provided as arguments to the `Execute` method.
## PJRT Concepts
### PjRtFutures & Async Computations
### Futures & Async Computations
If any part of a plugin is implemented asynchronously, it _must_ properly
implement futures.