| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 213027176
|
|
|
| |
Signed-off-by: hellcom <vitalii.stoianov.ua@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This improves build times when using the downloaded clang toolchain.
Additionally, remove '-B/usr/bin' flags from the cuda CROSSTOOL when using
the downloaded toolchain.
It was forcing 'clang' to first search for the linker in '/usr/bin',
preventing downloaded LLD from being selected.
PiperOrigin-RevId: 211430374
|
|
|
|
| |
PiperOrigin-RevId: 210975274
|
|\
| |
| |
| | |
PiperOrigin-RevId: 209623532
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Please approve this CL. It will be submitted automatically, and its GitHub pull request will be marked as merged.
Imported from GitHub PR #21373
A new version of nsync is released, this updates the workspace.bzl and adds nsync to the libs that can be unbundled. I've packaged nsync on Gentoo Linux and tested the full unbundled build.
The CMake build is also updated to the latest version, the patch is no longer required and is removed. I have tested the cmake build on my machine but the CI needs to test windows since I can't.
The last commits update ./configure to handle adding TF_SYSTEM_LIBS and an option to disable stripping.
@m3bm3b, can you review too?
Copybara import of the project:
- 3d224b29fcf699b84cf538e2d16e3dd4e78e6a91 workspace: update nsync dep to 1.20.1 by Jason Zaman <jason@perfinion.com>
- 34536b88bedc5a83ad939438a49a3cc53aea210c CMake: nsync: update to 1.20.1 by Jason Zaman <jason@perfinion.com>
- f2444ba218ae280e03710f936b249b6b650ea3dd third_party: unbundle nsync by Jason Zaman <jason@perfinion.com>
- 4386d8c4b01020ba1c979258e5102ac1947d2574 configure: Add TF_SYSTEM_LIBS handling by Jason Zaman <jason@perfinion.com>
- f3fd1f110781cfb8cc941241a69eb41114787bfd Merge 4386d8c4b01020ba1c979258e5102ac1947d2574 into a05c7... by Jason Zaman <jasonzaman@gmail.com>
COPYBARA_INTEGRATE_REVIEW=https://github.com/tensorflow/tensorflow/pull/21373 from perfinion:nsync 4386d8c4b01020ba1c979258e5102ac1947d2574
PiperOrigin-RevId: 209201545
|
| |\
| |/
|/| |
|
| | |
|
|\ \ |
|
| | | |
|
| | |\
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | |
| | | |
* Added nGraph bridge as a third_party to be built with TensorFlow based on user selection.
* Added a limited set of C++ unit tests to verify the correctness of the computation
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 205878953
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 205421605
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I was using bazel 0.12.0 and was getting the error:
file '@bazel_tools//tools/cpp:windows_cc_configure.bzl' does not contain symbol 'setup_vc_env_vars'
PiperOrigin-RevId: 205316270
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After this change, the windows build steps should be like:
https://docs.google.com/document/d/1oVYzPJVv8r5N9PecqwG74rY_QbqPH70IxBouBHdq5EI/edit?usp=sharing
PiperOrigin-RevId: 205295588
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 205165137
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 205147588
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 204919096
|
| |\ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 204859562
|
| | | |
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 204832902
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This simplifies ./configure process on Windows, we can remove them when we actually support the corresponding feature on Windows.
PiperOrigin-RevId: 204804112
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
cover up to Volta
PiperOrigin-RevId: 204606836
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
This is to keep the default configuration consistent with prebuilt TensorFlow.
PiperOrigin-RevId: 204513386
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After this change, to build TensorFlow with GPU support on Windows, you just need to follow the same procedure as Linux.
Also re-enable remote cache since the bug in b/111106393 has been fixed by the new wrapper script.
The clean-up of the wrapper scripts also made the build around 5 mins faster than using Bazel's msvc wrapper script.
PiperOrigin-RevId: 204105368
|
| | |
| | |
| | |
| | |
| | |
| | | |
configure.py respects CUDA_TOOLKIT_PATH instead of CUDA_INSTALL_PATH
PiperOrigin-RevId: 203591214
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Add KinesisDataset support for tensorflow Dataset
This fix is an attempt to add Kinesis support
for tensorflow's Dataset. Kinesis is provided by
AWS as a managed data streaming service. It is
similiar to Apache Kafka, often used in places
where maintaining a independent Kafka cluster on AWS
is not desirable or possible.
This fix adds the Kinesis support for tensorflow Dataset.
Similiar to the Kafka integration in tensorflow,
KinesisDataset outputs tf.string for records.
Test cases have also been added, which could be invoked manually.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Expose KinesisDataset in dataset_ops.cc
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Expose KinesisDataset in python wrapper
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Add test cases for KinesisDataset
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Update AWS library include files
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Add Bazel BUILD files
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Rename s3_crypto to aws_crypto
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Rename with_s3_support to with_aws_support
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Selectively add kinesis to tensorflow/contrib/BUILD
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Set different partition key and pylint fix.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Add missing modules in cmake's python_modules.txt
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Address review feedback
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 202613754
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 202585094
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 201110240
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 201033171
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 201011811
|
| | | |
|
| |/|
|/| | |
|
| | |
| | |
| | |
| | | |
Functional Dyn Ops
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These rules currently get written by configure.py script to WORKSPACE
file which is not ideal since (1) WORKSPACE file is tracked by git and
(2) we require users to manually delete the rules in order to
update/regenerate them.
Moving these rules into an external repo that is generated based on
several ENV variables set by the configure.py script. Modifying any
of these ENV variables will cause the rules to be updated.
PiperOrigin-RevId: 199388460
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* BUILD: dont force stripping
Build systems must not strip binaries, it makes it impossible for
distros to ship debugging symbols for packages.
bazel build has a --strip option to allow the user to generate stripped
binaries in a configurable way, that should be used instead.
https://fedoraproject.org/wiki/Packaging:Debuginfo
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces#Stripping
Signed-off-by: Jason Zaman <jason@perfinion.com>
* configure: add --strip=always to bazelrc
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Revert #18413. Too many internal test failures due to the name scope change caused by this change.
Revert #18192. Cannot use re2::StringPiece internally. Need alternative for set call. Will pull and clean this up in a separate change.
PiperOrigin-RevId: 197991247
|
|\| |
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
builds.
PiperOrigin-RevId: 197037867
|
|\| |
|
| |
| |
| |
| |
| |
| | |
version choices, and the '9.0' format is already present in the default).
PiperOrigin-RevId: 195855416
|
|/
|
|
|
| |
(#18986)
Remove all whitespace characters from the user specified tf_cuda_compute_capabilities string as this can results in errors during the split operation, and is easy for users to do as it is natural to insert a space after a comma
|
|
|
|
|
|
|
|
| |
Since py_runtime was introduced, Bazel ignores options such as
--force_python2 and --python2_path. Deleting to clean stuff up and
make sure people are not misled.
PiperOrigin-RevId: 193127681
|