| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
It already detects layout-changing copies and those are already left unchanged
by copy elision. Special case copies are also skipped because they are tagged
separately (SetCopyElisionAllowed)
PiperOrigin-RevId: 202574858
|
|
|
|
| |
PiperOrigin-RevId: 202572322
|
|
|
|
|
|
| |
could be updating the weights. This is specifically true on TPUS (tpu.repeat). Also, fix the `testDynamicRnnTrainLoop` unit test.
PiperOrigin-RevId: 202565323
|
|
|
|
|
|
| |
Detection app
PiperOrigin-RevId: 202564164
|
|
|
|
| |
PiperOrigin-RevId: 202551122
|
|
|
|
|
|
|
|
|
|
| |
The docs generator is not happy about the "\a" in "\approx" is becoming a "alert" escape sequence.
This should also fix a lot of the mathjax rendering on this page:
https://www.tensorflow.org/api_docs/python/tf/contrib/bayesflow/monte_carlo/expectation
PiperOrigin-RevId: 202550662
|
|
|
|
| |
PiperOrigin-RevId: 202546469
|
|
|
|
| |
PiperOrigin-RevId: 202544091
|
|
|
|
|
|
|
| |
Fixes #20160
REL_NOTES: tfdbg: Fix compatibility with `tf.keras.Model`s training on `tf.data.Dataset`s.
PiperOrigin-RevId: 202543231
|
|
|
|
|
|
| |
rely on this key to know whether TPU specific functionalities should be used.
PiperOrigin-RevId: 202542458
|
|
|
|
| |
PiperOrigin-RevId: 202539762
|
|
|
|
|
|
| |
No need to repeat an incompatible op time multiple times. Used set to ensure deterministic/same ordering in error message.
PiperOrigin-RevId: 202534388
|
|
|
|
| |
PiperOrigin-RevId: 202528760
|
|
|
|
|
|
| |
to build ops to use the corresponding free functions in namespace xla:: instead.
PiperOrigin-RevId: 202526945
|
|
|
|
|
|
| |
running multiple steps at a time using the `run_steps_on_dataset` API. It allows the user's step function to specify which outputs to emit at what frequency. Currently it only supports capturing output from the last step, but will soon be augmented to support other use cases such as output each N steps.
PiperOrigin-RevId: 202520245
|
|
|
|
| |
PiperOrigin-RevId: 202520102
|
|
|
|
|
|
|
|
| |
type: 'list'" out of ops.name_scope because the second arg of name_scope is default_name, not values.
Standardizes special_math_ops on the full name_scope(name, default_name, values) constructor.
PiperOrigin-RevId: 202519452
|
|
|
|
|
|
| |
The interpolate function currently just reformats tags, without adding any useful information. This change is part of a chain which will add this.
PiperOrigin-RevId: 202519204
|
|
|
|
|
|
| |
TF clip_ops, also added user input check for clipnorm and clipvalue >= 0 if set
PiperOrigin-RevId: 202516320
|
|
|
|
|
|
| |
ops at runtime.
PiperOrigin-RevId: 202514848
|
|
|
|
|
|
| |
into the other.
PiperOrigin-RevId: 202513508
|
|
|
|
|
|
|
| |
error_format_tag is a helper for building interpolatable strings as part of
a project to improve Python error messages in TensorFlow.
PiperOrigin-RevId: 202509392
|
|
|
|
|
|
| |
np.prod() to use np.int64 in a few places.
PiperOrigin-RevId: 202505308
|
|
|
|
|
|
| |
ops to use the corresponding free functions in namespace xla:: instead.
PiperOrigin-RevId: 202505306
|
|
|
|
| |
PiperOrigin-RevId: 202505228
|
|
|
|
| |
PiperOrigin-RevId: 202504925
|
|
|
|
|
|
| |
and `--input_exprs` headings to match option names.
PiperOrigin-RevId: 202504009
|
|
|
|
|
|
| |
Also enable cloud tpu profiler to detect the TF version for better version compatibility.
PiperOrigin-RevId: 202503162
|
|
|
|
| |
PiperOrigin-RevId: 202501055
|
|
|
|
| |
PiperOrigin-RevId: 202496488
|
|
|
|
| |
PiperOrigin-RevId: 202489637
|
|
|
|
|
|
| |
Only the name of the version is changing here; the version is unchanged.
PiperOrigin-RevId: 202486284
|
|
|
|
| |
PiperOrigin-RevId: 202472329
|
|
|
|
|
|
| |
We returned one-element tensors with uninitialized content, which msan didn't like.
PiperOrigin-RevId: 202463090
|
|
|
|
|
|
|
|
|
| |
The previous implementation recompiled the shape regex at every call
what is an expensive opertaion. The new implementation improves the hlo
text parsing time for very large models for up to 9x by eliminating this
overhead.
PiperOrigin-RevId: 202454354
|
|
|
|
|
|
| |
compatible with hlo string syntax.
PiperOrigin-RevId: 202445509
|
|
|
|
|
|
| |
Without domain propagation in dataflow analysis we end up in inconsistent domain instructions with BF16 as output and F32 as input. In case of tuple shapes these are not fixed by bfloat16_normalization, and later on they cause asserts once the domain instructions are removed.
PiperOrigin-RevId: 202442786
|
|
|
|
| |
PiperOrigin-RevId: 202423156
|
|
|
|
| |
PiperOrigin-RevId: 202419595
|
|
|
|
| |
PiperOrigin-RevId: 202415942
|
|
|
|
| |
PiperOrigin-RevId: 202412660
|
|
|
|
|
|
| |
using auto.
PiperOrigin-RevId: 202409729
|
|
|
|
| |
PiperOrigin-RevId: 202403235
|
|
|
|
| |
PiperOrigin-RevId: 202401460
|
|
|
|
| |
PiperOrigin-RevId: 202401380
|
|
|
|
| |
PiperOrigin-RevId: 202400843
|
|
|
|
| |
PiperOrigin-RevId: 202399218
|
|
|
|
|
|
|
|
|
|
| |
implementation.
Due to an issue with negative StridedSlice indices in TensorFlow, the end indices can specify degenerate slices when negative indices are used to shrink an axis (e.g. for tf.range(4)[-1], start is -1, end is 0, and stride is 1). This fix works around the issue by ignoring stop indices entirely when an axis is shrinking, since in order to be shrunk the length is by definition 1.
Fixes Issue #19260.
PiperOrigin-RevId: 202398678
|
|
|
|
| |
PiperOrigin-RevId: 202397475
|
|
|
|
|
|
|
|
| |
Change XLA lowering of QuantizeAndDequantizeV2/V3 to match the TF kernel much more closely. The main exception is the min_quantized and max_quantized values are calculated as floats to avoid the need for 64-bit integer math, which is not present on all accelerators.
Reformats unary_ops_test.py in passing, but on the whole I don't mind the reformatting.
PiperOrigin-RevId: 202395114
|