From 50f8f3f4349c0fcf9a2d7dbda82a7d228d4fd945 Mon Sep 17 00:00:00 2001 From: David Dunleavy Date: Tue, 12 Dec 2023 15:27:37 +0000 Subject: [PATCH] Add moving TSL into XLA RFC --- rfcs/20231212-moving-tsl-into-xla.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 rfcs/20231212-moving-tsl-into-xla.md diff --git a/rfcs/20231212-moving-tsl-into-xla.md b/rfcs/20231212-moving-tsl-into-xla.md new file mode 100644 index 0000000..2870ebb --- /dev/null +++ b/rfcs/20231212-moving-tsl-into-xla.md @@ -0,0 +1,23 @@ +# Moving TSL to XLA +| Status | Proposed | +| :------------ | :------------------------------------------------------ | +| **RFC #** | [100](https://github.com/openxla/community/pull/100) | +| **Authors** | David Dunleavy (ddunleavy@google.com) | +| **Sponsor** | Puneith Kaul (puneith@google.com) | +| **Updated** | 2023-12-12 + +## Objective +Move [TSL](https://github.com/google/tsl) to [XLA](https://github.com/openxla/xla). +## Proposal +TSL was originally utility and support libraries in TensorFlow needed by XLA. +Instead of moving the utility and support libraries directly to the openxla/xla repo, TSL was created anticipating +that other projects might want to move out of TensorFlow. In this case, TSL would provide common support code for +potentially many projects, not just XLA. +However, since TSL's creation over a year ago, XLA is the only direcet dependent of TSL, so we are in the process +of planning to move to TSL into XLA under the `tsl/` subdirectory. +We will use `bazel query` or similar to enforce that TSL remains independent on XLA, +such that projects who wish to depend on only TSL, but not XLA won't experience bloated binary sizes. +This work is currently planned to start in early Q1, so it would be great to hear any feedback or concerns with this +plan before January 12th, 2024. +Thanks! +