Update on "[torchgen] Add documentation for autogen keyword"

larryliu0820 · larryliu0820 · commit 33a80f31e5ca · 2022-08-17T11:23:41.000-07:00
This is a follow up for #81437. This PR explains what operator can use `autogen` and what will be generated. Also talked about generated kernels and where to find them. [ghstack-poisoned]
diff --git a/aten/src/ATen/native/README.md b/aten/src/ATen/native/README.md
@@ -484,11 +484,11 @@ wanted `const T*`.)
   autogen: my_op, my_op.out
 ```
 
-For an in-place variant of a native function (op name ends with an `_`), we offer the option to 
-generate a functional variant and an out= variant. If a functional variant is given, we will be 
-able to generate an out= variant. We don't support `autogen` for view ops, ops that bypass the 
-dispatcher and composite ops. We also generate kernels for generated ops, which merely copy and 
-return the result from the base ops. These generated kernels can be found in 
+For an in-place variant of a native function (op name ends with an `_`), we offer the option to
+generate a functional variant and an out= variant. If a functional variant is given, we will be
+able to generate an out= variant. We don't support `autogen` for view ops, ops that bypass the
+dispatcher and composite ops. We also generate kernels for generated ops, which merely copy and
+return the result from the base ops. These generated kernels can be found in
 `<gen-out>/aten/src/ATen/CompositeViewCopyKernels.cpp`.
 
 
