message: [XLA] LHLO-to-Ploop: explicitly construct ValueRange when building scf::ParallelOp
  The builder API is about to change in LLVM, which would lead to ambiguity in
  overload resolution in these cases. Proactively fix the issue by constructing
  ValueRange of steps explicitly before it is passed to the builder function.
diff: @@ -261,7 +261,7 @@ class ReduceOpConverter : public OpConversionPattern<xla_lhlo::ReduceOp> {
  rewriter->setInsertionPointToStart(outer.getBody());
  }
  scf::ParallelOp inner = rewriter->create<scf::ParallelOp>(
  - loc, reduce_lower, reduce_upper, reduce_step, init_value);
  + loc, reduce_lower, reduce_upper, reduce_step, ValueRange(init_value));
  Value reduction_result = *inner.getResults().begin();
  SmallVector<Value, 1> out_indices;
  @@ -406,7 +406,7 @@ class ReduceWindowOpConverter
  rewriter->create<ConstantIndexOp>(loc, window_dim.getSExtValue()));
  }
  auto window_loop = rewriter->create<scf::ParallelOp>(
  - loc, window_lower, window_upper, window_step, init_value);
  + loc, window_lower, window_upper, window_step, ValueRange(init_value));
  Value reduction_result = *window_loop.getResults().begin();
  auto output_ivs = output_loop.getInductionVars();
  