# Registering new compiler backend in Pytorch2.0

**URL:** <https://dev-discuss.pytorch.org/t/registering-new-compiler-backend-in-pytorch2-0/1092>\
**Category:** compiler\
**Created:** [March 3, 2023, 10:29am UTC](https://dev-discuss.pytorch.org/t/registering-new-compiler-backend-in-pytorch2-0/1092 "2023-03-03T10:29:34Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![AR51](https://avatars.discourse-cdn.com/v4/letter/a/58f4c7/32.png) [@AR51](https://dev-discuss.pytorch.org/u/AR51)\
**Post date:** [March 20, 2023, 10:07am UTC](https://dev-discuss.pytorch.org/t/registering-new-compiler-backend-in-pytorch2-0/1092/7 "2023-03-20T10:07:09Z")

</div>

I got. I was able to get to it. Thanks for the help.  
Another question is how we are doing mid-layer integration at the Aten FX graph layer.  
I’ve my own backend implemented in the cpp with my own data structures. I want to convert the aten FX graph into my own data structure graph which my backend can emit the binary out and run on the respective hardware. Can you give some pointers on that?? How are we providing control from python to cpp and its integration?

I’ve posted the question in: [How do we do mid layer integration after Aten fx graph](https://dev-discuss.pytorch.org/t/how-do-we-do-mid-layer-integration-after-aten-fx-graph/1140)

---

_[View the full topic](https://dev-discuss.pytorch.org/t/registering-new-compiler-backend-in-pytorch2-0/1092)._
