// operations).  Such a cluster can fail compilation (in way that
    // MarkForCompilation could not have detected) if the CPU JIT is not
    // linked in.
    //
    // So bail out of _XlaCompile in this case, and let the executor handle
    // the situation for us.
    const Status& status = compiler_for_platform.status();
    if (status.code() == error::NOT_FOUND) {

  effects.emplace_back(MemoryEffects::Write::get(),
                       ResourceEffects::_XlaRun::get());

  // Conservatively mark resource handles as read and write, as without
  // analyzing _XlaCompile, there is not sufficient information to determine
  // effects on resources.
  for (Value value : getArgs()) {
    MarkResourceAsReadAndWrite(value, effects);
  }
}

node and associated metadata.}]>:$key,
    Res<TF_BoolTensor, [{If the `must_compile` attr is false the _XlaCompile op
can decide not to compile the clusters based on some profitability
heuristics.  In that case `compilation_successful` is false if _XlaCompile
chose not to compile the cluster.  If the `must_compile` attr is true then
_XlaCompile always attempts to compile the cluster and