The `bzl_library(defs_bzl)` dependency on `lit_bzl` is left commented out,
for now, because it transitively, through rules_cc, depends on a
bazel_skylib target (`@bazel_skylib/rules/directory/<something>`) that
isn't present in the version of bazel_skylib currently being used.
Because these bzl_library targets aren't really used in OSS, this missing
dependency (until bazel_skylib is upgraded) should be OK.
PiperOrigin-RevId: 757872351
619575611 by A. Unique TensorFlower<gardener@tensorflow.org>:
Run buildifier on all files where it sorts loads differently
--
619498661 by A. Unique TensorFlower<gardener@tensorflow.org>:
[XLA:GPU][IndexAnalysis] Rename GetDefaultThreadIdToOutputIndexingMap to GetDefaultThreadIdIndexingMap.
The "output" part was a bit confusing. We use this function for threadId->input
mapping as well.
--
619490165 by A. Unique TensorFlower<gardener@tensorflow.org>:
Convert S8 to BF16 in one step without going though F32.
--
PiperOrigin-RevId: 619575611
In the long term, all uses of bazel-genfiles will be replaced with bazel-bin. Starlark rules should only set `output_to_genfiles = True` when required for compatibility with other rules or tools that make assumptions about the location of output files.
Note that Bazel already defaults to `--incompatible_merge_genfiles_directory`, which makes the distinction moot anyway.
PiperOrigin-RevId: 611762875
Update TFLite build rules to use Flatbuffer v2.0.5
Also following changes are made:
- Updated schema_generated.h for 2.0.5.
- Fix a regression in flatbuffer_export.cc
- Update tensor comparison logic in quantize_model_test.cc
PiperOrigin-RevId: 454483837
root of the 3P repository. But BUILD.bazel was also being interpreted by
bazel as the BUILD file for the //third_party/name folder, which is wrong.
This change renames those files to name.BUILD, a convention already being
used by some packages.
PiperOrigin-RevId: 409278565
Change-Id: Ib99c3474ec0b20d04cdb9d828f68c8303caec5fe
To compile flatbuffers definition Bazel starts the flatbuffers compiler
flatc which is potentially built using a custom
toolchain and hence requires a set up LD_LIBRARY_PATH.
Ommitting the `use_default_shell_env` (defaulting to false) clears the
whole environment and the binary may try to use older system libs such
as /lib64/libstdc++.so causing it to fail in case it is (much) older
than the used libstdc++ from the custom toolchain which is very common
in HPC environments.
Hence I added `use_default_shell_env = True` as already done in e.g.
`_local_genrule_impl`.
Replace calls to `third_party_http_archive` with calls to `tf_http_archive` alias.
Disable 'mirror.tensorflow.org' check. A number of users don't seem to follow the requirements, which were not checked correctly before.
This wasn't discovered by presubmits because the check is in the repo rule, which only triggers if the repo is actually used.
PiperOrigin-RevId: 359355039
Change-Id: Ieddab6fd91b96e6e22afccdad21c8fa30b795ff4
