| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
PiperOrigin-RevId: 201110240
|
|
|
|
| |
PiperOrigin-RevId: 201073792
|
|
|
|
| |
PiperOrigin-RevId: 201033171
|
|
|
|
| |
PiperOrigin-RevId: 201011811
|
|
|
|
| |
PiperOrigin-RevId: 198518885
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PiperOrigin-RevId: 196640024
|
|
|
|
|
|
| |
NVFlex.o in cuda_9_0/lib64/libculibos.a has buggy .eh_frame, which overlaps with .rela.rodata R_X86_64_PC32 relocations and makes it not able to be linked with LLD.
PiperOrigin-RevId: 196155873
|
|
|
|
| |
PiperOrigin-RevId: 195113702
|
|
|
|
| |
PiperOrigin-RevId: 194372273
|
|
|
|
| |
PiperOrigin-RevId: 194096341
|
|
|
|
| |
PiperOrigin-RevId: 194031845
|
|
|
|
| |
PiperOrigin-RevId: 192850372
|
|
|
|
| |
PiperOrigin-RevId: 191672761
|
|
|
|
|
|
| |
In most cases it seems to be not used.
PiperOrigin-RevId: 191407383
|
|
|
|
|
|
| |
This reverts commit 4e108ef30d7cd7ae5e1c550ec5ae27e79b8c6e39.
PiperOrigin-RevId: 191391075
|
|
|
|
| |
PiperOrigin-RevId: 190953197
|
|
|
|
| |
PiperOrigin-RevId: 190858242
|
|
|
|
| |
PiperOrigin-RevId: 190835392
|
|
|
|
| |
PiperOrigin-RevId: 190051589
|
|
|
|
| |
PiperOrigin-RevId: 189258641
|
|
|
|
|
|
| |
in the final executable, which causes link warnings/errors (different linker behaves differently). The optimal way to fix this is to link the binary with shared library, however, the libraries are NVIDIA-proprietary, not all of them have shared version (for example: cuda_9_0/lib64/libculibos.a)
PiperOrigin-RevId: 189254317
|
|
|
|
| |
PiperOrigin-RevId: 189231636
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The implementation of tensorflow/core/platform/default/mutex.h uses the nsync
library, so mutex.h has included nsync header files.
This has been awkward, because each TensorFlow build (bazel, cmake, make, plus
the instructions for compiling individual custom ops, on all the various
platforms) has needed to handle the include paths correctly, reaching into a
package that is downloaded separately from TensorFlow itself.
This change avoids that awkwardness, instead taking on two different
irritations:
- mutex.h now defines two structs that are large enough and aligned enough to
contain an nsync_mu and an nsync_cv. This is an abstraction violation,
because TensorFlow's source should not need to know how big these data
structures are. However, this is unlikely to cause problems because:
1) this is checked by a static assertion in mutex.cc, so we will notice
immediately should a change be needed, and
2) this will likely never fail because we have no intent of allowing nsync's
data strcutures to get bigger.
- The methods of mutex and condition_variable can no longer be inlined, because
that too would require mutex.h to include the nsync header files. (Or we'd
need to declare the nsync functions directly in mutex.h, which would be
another abstraction violation.) However, this is a small imposition
because the overhead of a procedure call is typically small.
The assumption behind this CL is that these irritations are less important than
the ongoing frustration of maintaining the complex include path in multiple build
systems.
PiperOrigin-RevId: 189079523
|
|
|
|
| |
PiperOrigin-RevId: 186674197
|
|
|
|
|
|
| |
locally.
PiperOrigin-RevId: 185439892
|
|
|
|
| |
PiperOrigin-RevId: 184897758
|
|
|
|
| |
PiperOrigin-RevId: 184715822
|
|
|
|
| |
PiperOrigin-RevId: 183347199
|
|
|
|
| |
PiperOrigin-RevId: 182258809
|
|
|
|
|
|
| |
op_gen_overrides.pbtxt are a part of tensorflow/core/api_def/base_api/.
PiperOrigin-RevId: 181386873
|
|
|
|
| |
PiperOrigin-RevId: 180301735
|
|
|
|
| |
PiperOrigin-RevId: 179971055
|
|
|
|
| |
PiperOrigin-RevId: 179953488
|
|
|
|
| |
PiperOrigin-RevId: 179881638
|
|
|
|
|
|
|
|
|
|
| |
This change adjusts the build options for tf_cc_test targets so that
they can be built for Android devices by default. Many targets will
still need additional options on a per-target basis.
Android requires that executables be compiled with `-pie`.
PiperOrigin-RevId: 179729092
|
|
|
|
| |
PiperOrigin-RevId: 179263865
|
|
|
|
| |
PiperOrigin-RevId: 179260538
|
|
|
|
| |
PiperOrigin-RevId: 179258973
|
|
|
|
| |
PiperOrigin-RevId: 179256571
|
|
|
|
| |
PiperOrigin-RevId: 178618409
|
|
|
|
| |
PiperOrigin-RevId: 177851421
|
|
|
|
| |
PiperOrigin-RevId: 177784085
|
|
|
|
| |
PiperOrigin-RevId: 177661127
|
|
|
|
| |
PiperOrigin-RevId: 177555877
|
|
|
|
|
|
|
| |
For example toolchains with clang may set -Oz which is more analogous to gcc's
-Os. -Os for clang is closer to -O2.
PiperOrigin-RevId: 177347371
|
|
|
|
|
|
| |
C++ API. Also, updating UpdateDocs method to ApiDef to replace names in docs.
PiperOrigin-RevId: 176167953
|
|
|
|
|
|
|
|
| |
--copts are passed to both c++ and c (so is redundent with --cxxopts).
Configs passed to "bazel build" are inherited by "bazel run" and "bazel test".
Also removed some unused configs.
PiperOrigin-RevId: 175326697
|
|
|
|
| |
PiperOrigin-RevId: 174539513
|
|
|
|
| |
PiperOrigin-RevId: 174248361
|