Kernels fails with contract violation (support scalar outputs) about diospyros HOT 4 OPEN

We currently fail on this kernel because the output is a scalar, so a workaround is to have the output be a 1-element array.

I can implement scalar outputs, but it doesn't seem particularly useful right now because we don't have any rewrite rules for horizontal vector operations (so the example kernels won't see any improvement). Is there a use case here where some more complicated, per-elements computations feed into a final horizontal accumulation?

from diospyros.

The particular function I have is inlined so it's possible that it may get called inside a loop. Though in general I don't know if this is a valid assumption. Do the multiple function subroutines get inlined into the dataflow graph before the dios compiler gets to processing it? If so then maybe we're ok and I'll just wrap it with a loop.

from diospyros.

Diospyros essentially inlines everything into the outermost function of what is passed in. So yes, if the calling context is a loop here, it would be more useful to pass the surrounding loop context, something like:

#define SIZE 8
void foo(float x_in, float y_in[3], float z_out) {
  float acc = 0.0f;
  for (int a = 0; a < 3; a++) {
    acc = acc + x_in * y_in[a];
  }
  z_out = acc;
}

void loop(..., float all_outs[SIZE]) {
    for (int a = 0; a < SIZE; a++) {
        all_outs[a] = foo(...);
    }
}

In that case, the inner function foo should not need the input/output parameters to be tagged, as long as the outer (later) function does have the tags.

from diospyros.

Better error message for now in 0ac745b

from diospyros.