- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 44 for within (0.28 sec)
-
ci/official/wheel_test/README.md
init files creation process and is subsequently stored in the wheel file after the build. It also contains a few paths that cannot be directly imported. These paths point to attributes or sub-modules within a module's namespace, but they don't correspond to an actual file or directory on the filesystem. The list of such paths is stored in the packages_for_skip variable and will be skipped during the test. ##### How to Build
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Aug 31 18:17:57 GMT 2023 - 3.3K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/aarch64_clang.bazelrc
build --distinct_host_configuration=false # Disable clang extension that rejects type definitions within offsetof. # This was added in clang-16 by https://reviews.llvm.org/D133574. # Can be removed once upb is updated, since a type definition is used within # offset of in the current version of ubp. # See https://github.com/protocolbuffers/upb/blob/9effcbcb27f0a665f9f345030188c0b291e32482/upb/upb.c#L183.
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Tue Nov 21 12:25:39 GMT 2023 - 6.3K bytes - Viewed (0) -
RELEASE.md
* In `Layer.call`, `AutoCastVariable`s will no longer be casted within `MirroredStrategy.run` or `ReplicaContext.merge_call`. This is because a thread local variable is used to determine whether `AutoCastVariable`s are casted, and those two functions run with a different thread. Note this only applies if one of these two functions is called within `Layer.call`; if one of those two functions calls `Layer.call`,
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Apr 29 19:17:57 GMT 2024 - 727.7K bytes - Viewed (8) -
.bazelrc
# dbg: Build with debug info # # TF version options; # v2: Build TF v2 # # Feature and Third party library support options: # xla: Build TF with XLA # tpu: Build TF with TPU support # cuda: Build with CUDA support. # cuda_clang Build with CUDA Clang support. # rocm: Build with AMD GPU support (rocm)
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu May 02 19:34:20 GMT 2024 - 52.8K bytes - Viewed (2) -
ci/official/README.md
- Uses `pycpp.sh`, `code_check_changed_files.sh` These "env" files match up with an environment matrix that roughly covers: - Different Python versions - Linux, MacOS, and Windows machines (these pool definitions are internal) - x86 and arm64 - CPU-only, or with NVIDIA CUDA support (Linux only), or with TPUs ## How to Test Your Changes to TensorFlow
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
CONTRIBUTING.md
`--config=dbg` to Bazel will build with debugging information and without optimizations, allowing you to use GDB or other debuggers to debug C++ code. For example, you can build the pip package with debugging information by running: ```bash bazel build --config=dbg //tensorflow/tools/pip_package:build_pip_package ``` TensorFlow kernels and TensorFlow's dependencies are still not built with
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0) -
ci/official/requirements_updater/README.md
## Requirements updater Requirements updater is a standalone tool, intended to simplify process of updating requirements for multiple minor versions of Python. It takes in a file with a set of dependencies, and produces a more detailed requirements file for each version, with hashes specified for each dependency required, as well as their sub-dependencies. ### How to update/add requirements
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Tue Jan 23 02:14:00 GMT 2024 - 3.9K bytes - Viewed (1) -
ci/official/envs/linux_arm64_onednn
# Copyright 2023 The TensorFlow Authors. All Rights Reserved. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS,
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Tue Feb 06 19:26:00 GMT 2024 - 810 bytes - Viewed (0) -
ci/official/envs/macos_x86_cross_compile
# Copyright 2023 The TensorFlow Authors. All Rights Reserved. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS,
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri Feb 02 23:38:12 GMT 2024 - 1.2K bytes - Viewed (0) -
WORKSPACE
# # The cascade of load() statements and tf_workspace?() calls works around the # restriction that load() statements need to be at the top of .bzl files. # E.g. we can not retrieve a new repository with http_archive and then load() # a macro from that repository in the same file. load("@//tensorflow:workspace3.bzl", "tf_workspace3") tf_workspace3() load("@//tensorflow:workspace2.bzl", "tf_workspace2")
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Fri Apr 05 22:27:48 GMT 2024 - 3K bytes - Viewed (2)