diff options
author | Geoffrey Irving <geoffreyi@google.com> | 2016-01-12 08:06:56 -0800 |
---|---|---|
committer | Vijay Vasudevan <vrv@google.com> | 2016-01-12 08:06:56 -0800 |
commit | cbff45c03b96a2efb2bd45a54cd0facb12007fa8 (patch) | |
tree | f3eec525854ec4de4efec496fa521fe26940d5c6 /RELEASE.md | |
parent | ca34dbe4e8f3fe6fc1e0e209662f93afe4ff9614 (diff) |
Add GraphDef version 6 implementing scalar strictness, but don't use it
The kAllowLegacyScalars flag is now gone. Instead, scalar strictness now
depends on the GraphDef version: we are lenient below 6 and strict with 6
and above. The current GraphDef version is still 5; new graphs will not
yet use the new version by default.
Outside of PLATFORM_GOOGLE, this change has no effect since the code was
already scalar strict.
The TensorShapeUtils versions of IsLegacyScalar and IsLegacyVector are also
gone; users should now get them from OpKernel.
The GraphDef version history has been moved to core/public/version.h to
minimize the number of files that must be changed in future CLs.
Change: 111947842
Diffstat (limited to 'RELEASE.md')
-rw-r--r-- | RELEASE.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/RELEASE.md b/RELEASE.md index 358e2aef1c..942781c829 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -10,6 +10,11 @@ * The image processing ops do not take `min` and `max` inputs any more, casting safety is handled by `saturate_cast`, which makes sure over- and underflows are handled before casting to data types with smaller ranges. +* For C++ API users: `IsLegacyScalar` and `IsLegacyVector` are now gone from + `TensorShapeUtils` since TensorFlow is scalar strict within Google (for + example, the shape argument to `tf.reshape` can't be a scalar anymore). The + open source release was already scalar strict, so outside Google `IsScalar` + and `IsVector` are exact replacements. ## Bug fixes @@ -19,6 +24,7 @@ It will break tests that compare a generated `GraphDef` to a golden serialized `GraphDef`. + # Release 0.6.0 ## Major Features and Improvements |