Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for tf_api_version (0.29 sec)

  1. tensorflow/BUILD

    # This flag specifies whether TensorFlow 2.0 API should be built instead
    # of 1.* API. Note that TensorFlow 2.0 API is currently under development.
    config_setting(
        name = "api_version_2",
        define_values = {"tf_api_version": "2"},
        visibility = ["//visibility:public"],
    )
    
    # This flag specifies the file prefixes to strip from the file imports
    # when generating python apis.
    config_setting(
        name = "litert_prefixes",
    Registered: Tue Dec 30 12:39:10 UTC 2025
    - Last Modified: Wed Nov 12 19:21:56 UTC 2025
    - 53.1K bytes
    - Viewed (0)
  2. .bazelrc

    common:windows_x86_cpu_2022 --platforms="//tensorflow/tools/toolchains/win2022:windows_ltsc2022_clang"
    
    # Options to build TensorFlow 1.x or 2.x.
    # TODO(kanglan): Change v2's define to default behavior
    common:v2 --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
    
    # Enable all targets in XLA
    common:cpu_cross --define=with_cross_compiler_support=true
    
    # Disable XLA on mobile.
    Registered: Tue Dec 30 12:39:10 UTC 2025
    - Last Modified: Fri Dec 26 23:20:26 UTC 2025
    - 56.8K bytes
    - Viewed (0)
  3. RELEASE.md

            _reduce_jacobian_det_over_event does not handle scalar ILDJ
            implementations properly.
        *   In tf eager execution, allow re-entering a GradientTape context.
        *   Add tf_api_version flag. If --define=tf_api_version=2 flag is passed in,
            then bazel will build TensorFlow API version 2.0. Note that TensorFlow
            2.0 is under active development and has no guarantees at this point.
    Registered: Tue Dec 30 12:39:10 UTC 2025
    - Last Modified: Tue Oct 28 22:27:41 UTC 2025
    - 740.4K bytes
    - Viewed (3)
Back to top