PrimTorch: How backend/compiler writers interact with various IRs

[Minerva_Yu]

@Minerva_Yu

For Core ATen IR is the subset of aten operators, the way I use it is the same with former, i.e. through “native_functions.yaml”. ( But how could I distinguish who are the “Core ATen” ops and who are the “ATen” ones? )

For the second question, some new discoveries:
ops in “native_functions.yaml” file with a tag “core” are the Core ATen IRs.

And by trying with the inplace variants torch.abs_(x), FX graph found is as follow:

...
abs_1: f16[2048] = torch.ops.aten.abs.default(arg0_1)
...
copy_: f16[2048] = torch.ops.aten.copy_.default(arg0_1, abs_1);  arg0_1 = None
...

Although I have not found where the abs_ ops is decomposed to abs and copy_ ops. Probably that is some magic with def register_inplace() function.