| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
The tile shape can be deduced based on the tile assignment and then HLO
shape and by not storing it in the sharding we can give more flexibility
to the compiler to decide the data layout.
PiperOrigin-RevId: 207860794
|
| |
|
|
|
|
|
|
|
| |
Currently Literal classes sits in literal_util.{h,cc} instead of literal.{h,cc}.
It also contains helper functions that are better fit to be their own separate
class/namespace. This change starts this process by moving most static factory
methods to LiteralUtil namespace.
PiperOrigin-RevId: 203217065
|
| |
|
|
|
|
|
|
| |
Now that we're using the parser inside of xla/service, it's awkward for
it to live inside of xla/tools, because everything else in there is a
standalone tool. We've already had one person be confused by this.
PiperOrigin-RevId: 198935921
|
| |
|
|
|
|
| |
use.
PiperOrigin-RevId: 197825588
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I didn't remove the enum itself, but after this change removing the enum should
be a simple NFC change (famous last words!).
This will make it easier to implement BatchDot on CPU.
The change removes usages of kTransposeDot by:
- Teaching TransposeFolding to "fuse" transposes into dots by flipping the
lhs_contracting_dims/rhs_contracting_dims fields.
- Replacing the notion of transpose_lhs/transpose_rhs in the IR emitters with
"has a non-canonical LHS contraction dimension"/"has a non-canonical RHS
contraction dimension" where the canonical LHS and RHS contraction dims [0]
are 1 and 0.
Some tests were getting away with creating Dot instructions with their
dimensions numbers unset. I've fixed these to create canonical dot operations
instead.
It is possible (but hard to tell without trying) that some of the IR emission
logic and Eigen runtime calls can now be simplified further. For instance,
instead of passing in a `transpose_lhs` and `transpose_rhs` to the Eigen GEMM
routines, we could instead pass in the LHS and RHS contraction dimensions
directly.
[0] See HloInstruction::CreateCanonicalDot.
PiperOrigin-RevId: 195514907
|
| |
|
|
|
|
|
|
| |
After this change a test can use op::Shape("f32[7,11]") instead of the
longer and harder to read op::Shape(ShapeUtil::MakeShape(F32, {7, 11}))
format.
PiperOrigin-RevId: 194373704
|
| |
|
|
|
|
|
| |
These new matchers can be used in tests in combination to the existing
HLO opcode matchers to better verify a generated HLO graph.
PiperOrigin-RevId: 194082100
|
| |
|
|
|
|
| |
Now with less build breakage!
PiperOrigin-RevId: 183458987
|
| |
|
|
| |
PiperOrigin-RevId: 183312680
|
| |
|
|
| |
PiperOrigin-RevId: 183296506
|
| |
|
|
|
|
|
|
| |
Append the parameter number to the fusion parameter name, and use the parameter
name rather the instruction name in creating the new parameter.
Show the paramameter number when printing out parameter instructions.
Change: 153752424
|
|
|
Change: 153159175
|
A. Unique TensorFlower
Kay Zhu
Justin Lebar
Sanjoy Das