Hi,
Apologies for the delayed reply. I don't entirely follow your question on pattern matching - it seems like what you're talking about there is already possible. Regarding the query about the Ethos-U partitioning/legalizing flow, I think the two routes are essentially equivalent. We partition first (via composite functions) and then legalize, but I agree it would be equally valid to legalize first and then partition. In terms of simplicity, I think both are just as simple. There are fundamentally two pieces of logic that need implementing - something to check whether a given pattern is supported by your offload target, and something to mutate the Relay into your target's Relay 'dialect'. If you legalize first, then you must do both of these things in the same legalization pass. If you partition first, then you test 'supportedness' in the partitioner and subsequently do the mutation in the partitioned module. The code that needs writing is about the same, just positioned differently. --- [Visit Topic](https://discuss.tvm.apache.org/t/how-to-add-my-custom-relay-node-to-pattern-matcher-ethosu-example/11498/3) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/959f7d0989a2ec5712ff5175130133d4220bd65e12087bfb3278b6947cac2f54).
