Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for buyers (0.15 sec)

  1. tensorflow/c/eager/c_api_experimental.h

                                                       size_t proto_len,
                                                       TF_Status* status);
    
    // TODO(b/166642410): It would be nice, for custom devices and for other users,
    // to have a non-string representation of devices (TF_Device) extracted from
    // tensors/ops/etc. and usable in APIs like OpSetDevice/ResetOp/etc.
    
    #define TFE_CUSTOM_DEVICE_VERSION 4
    
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Feb 21 22:37:46 GMT 2024
    - 39.5K bytes
    - Viewed (0)
  2. tensorflow/c/c_api_experimental.h

    //     in `input_shapes`.
    //
    // The results are returned in `output_shapes` and
    // `output_resource_shapes_and_types`. The caller is responsible for freeing the
    // memory in these buffers by calling `TF_DeleteShapeAndTypeList`.
    TF_CAPI_EXPORT extern void TFE_InferShapes(
        TFE_Op* op, TF_ShapeAndTypeList* input_shapes, TF_Tensor** input_tensors,
        TF_ShapeAndTypeList* input_tensor_as_shapes,
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Apr 27 21:07:00 GMT 2023
    - 15.1K bytes
    - Viewed (0)
  3. tensorflow/c/eager/tape.h

      // If `persistent` is true, GradientTape will not eagerly delete backward
      // functions (and hence the tensors they keep alive). Instead, everything
      // is deleted in ~GradientTape. Persistent GradientTapes are useful when
      // users want to compute multiple gradients over the same tape.
      explicit GradientTape(bool persistent) : persistent_(persistent) {}
      ~GradientTape() {
        for (const auto& pair : op_tape_) {
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Tue Apr 02 12:40:29 GMT 2024
    - 47.2K bytes
    - Viewed (1)
  4. tensorflow/c/experimental/filesystem/filesystem_interface.h

      /// of them. Ownership of options and buffers therein belongs to the caller
      /// and any buffers need to be allocated through filesystem allocation API.
      /// Filesystems may choose to ignore configuration errors but should at least
      /// display a warning or error message to warn the users.
      ///
      /// Plugins:
      ///   * Must set `status` to `TF_OK` if options are updated.
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri May 27 17:36:54 GMT 2022
    - 53.1K bytes
    - Viewed (0)
Back to top