[compiler FE/onert-micro] Support CircleGRU

[BalyshevArtem]

What

Let's support CircleGRU as custom circle operation in compiler FE and onert-micro.

Why

Some target models for onert-micro contains such pattern. This conversion accelerates the execution of target models in onert-micro.

How

• Support in Compiler FE Compiler FE: Enable CircleGRU Op #12320
• Support in onert-micro # [onert-micro] Add GRU forward execution #13746

[BalyshevArtem]

First draft to check impact #11840 of such conversion

[BalyshevArtem]

Before conversion

Main graph:

Cond graph:

Body graph:

[BalyshevArtem]

After conversion:

[seanshpark]

Are you going to use custom_gru as the op type?
Op is CustomOp and custom code is custom_gru. This is odd.
I would be better to rename this to some meaningful name.
What kind of GRU is this? Plz add some details about this.

[seanshpark]

@lemmaa , @hseok-oh , what do you think of adding new Circle Op CIR_GRU = -5 in circle schema?

• CIR_ prefix is to avoid future conflict when GRU is added in tflite , just optional, not the main point.

[BalyshevArtem]

Are you going to use custom_gru as the op type? Op is CustomOp and custom code is custom_gru. This is odd. I would be better to rename this to some meaningful name. What kind of GRU is this? Plz add some details about this.

Yes, use CustomOp with custom code - CUSTOM_GRU.

I would be better to rename this to some meaningful name

Smth like CIRCLE_CUSTOM_GRU?

What kind of GRU is this?

GRU operation that is obtained using tf.keras.layers.GRU(units=num_units, activation='tanh') and where return_sequences=False. After conversion from tf into tflite it has pattern like #12263 (comment)

After supporting such pattern we will support with return_sequences=True

[BalyshevArtem]

@lemmaa , @hseok-oh , what do you think of adding new Circle Op CIR_GRU = -5 in circle schema?

It can be helpful for us.

[seanshpark]

Smth like CIRCLE_CUSTOM_GRU?
GRU operation that is obtained using tf.keras.layers.GRU(units=num_units, activation='tanh')

How about CircleGru ?
(FYI #12242 (comment) for existing codes)

[BalyshevArtem]

How about CircleGru ?

For me good. Is it for custom code, right?

[seanshpark]

Is it for custom code, right?

Yes, as @lemmaa and @hseok-oh hasn't replied yet.

@lemmaa , @hseok-oh , PTAL

[lemmaa]

Is it for custom code, right?

Yes, as @lemmaa and @hseok-oh hasn't replied yet.

@lemmaa , @hseok-oh , PTAL

LGTM. This will be useful for GRU acceleration. :)

[hseok-oh]

Is it for custom code, right?

Yes, as @lemmaa and @hseok-oh hasn't replied yet.

@lemmaa , @hseok-oh , PTAL

Good.

[seanshpark]

@BalyshevArtem , we are good to go with new CircleGRU IR.
If you like, you can introduce this IR, or I can work on this (maybe a little bit faster to land).

[hseok-oh]

@BalyshevArtem, @seanshpark In schema, does CircleGRU need CircleGRUOptions for OP's parameter?

[seanshpark]

from the draft #11840 , I think there's no option, for some attributes, is needed.
but would be better to get confirm from @BalyshevArtem

[BalyshevArtem]

@BalyshevArtem, @seanshpark In schema, does CircleGRU need CircleGRUOptions for OP's parameter?

Actually for future good to have, I think CircleGRUOptions have to contain these fields:

1. fused_activation_function
2. return_sequences - bool value
3. time_major - bool value

[BalyshevArtem]

from the draft #11840 , I think there's no option, for some attributes, is needed.

If we can obtain CircleGRUOptions than I will add in the draft it

[BalyshevArtem]

@BalyshevArtem , we are good to go with new CircleGRU IR.
If you like, you can introduce this IR, or I can work on this (maybe a little bit faster to land).

Thank you, I will try to add it)

[seanshpark]

@BalyshevArtem , please try with this in your draft (I think you already know this)

table GRUOptions {
  fused_activation_function:ActivationFunctionType;
  return_sequences : bool;
  time_major : bool;
}

[seanshpark]

this is active