@manupa-arm that's the ultimate goal to solve 2 problems currently the merge composite pass facing:
1. As you pointed out, the current approach to specify the composite pattern requires users to make lots of similar patterns. This problem was reported by @masahi and @jonso if I remember correctly. With the pattern language, we will have a unified and general pattern specification. 2. The current merge composite pass includes a pattern matching algorithm, but it actually uses a small Relay graph as a pattern to perform pattern matching. This, however, would encounter many issues when handling Relay graph node attributes. On the other hand, the graph nodes of pattern language include all required information for matching, and the pattern language infra covers necessary analysis such as dominator analysis to make the pattern matching more robust. Consequently, we should use pattern language infra to implement merge composite. By doing so, 1) we don't have to worry the matching algorithm anymore, and 2) users only need to learn one unified pattern language that TVM will use everywhere in the future. btw, the merge composite related discussion is not directly related to this topic so I'd suggest we stop the merge composite discussion and focus on the Ethos-N here (@Leo-arm sorry about that!). Anyone interested in the merge composite is welcome to raise a new topic. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/10) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/2854b72601b16304ab67b775c8011ba468921e24c0dd1ac200af985d2a3d596e).
