diff options
| author |  A. Unique TensorFlower <gardener@tensorflow.org> | 2018-09-19 12:55:02 -0700 |
|---|---|---|
| committer | TensorFlower Gardener <gardener@tensorflow.org> | 2018-09-19 12:58:14 -0700 |
| commit | c95353498e180e50f701dcb8331b994d9e5fad0b (patch) | |
| tree | 7e1b048f3834c997149dd144421b4bddc547d0e4 /CODE_OF_CONDUCT.md | |
| parent | ff11877b101fe9c19021e8d7b43841031eb71cc3 (diff) | |
Fixes in ResolveReorderAxes.
The main issue is we were keeping the input array, updating it in place and discarding the output array. That was a problem when the input array had multiple consumer ops. Now we're keeping the output array instead, which is the correct thing to do. However, in order to minimize disruption, we keep using the input array's name whenever possible, by means of some array renamings.
PiperOrigin-RevId: 213678219
Diffstat (limited to 'CODE_OF_CONDUCT.md')
0 files changed, 0 insertions, 0 deletions