f^(hddlmZddlmZmZmZmZddlmZm Z ddl m Z da da e dedZe ded efd Ze dd Zd d dZe dGddeZy ))contextmanager)_format_import_block GraphModulereduce_graph_modulereduce_package_graph_module)PackageExporter sys_importer) compatibilityF)is_backward_compatiblec#8K t}dad|ay#awxYww)a@ Skip using lazy graph module disregarding the setting of _use_lazy_graph_module. Use to skip _LazyGraphModule when testing inductor torchscript related backend. torch.jit.script a _LazyGraphModule results in following error: https://gist.github.com/shunting314/5143654c8084aed84ecd19b818258a69 TN)"_force_skip_lazy_graph_module_flag)priors Y/var/www/skyplay_api_hub/venv/lib/python3.12/site-packages/torch/fx/_lazy_graph_module.py_force_skip_lazy_graph_modulers%32-1* -2*U*s  should_usec#JK t}|xrt ad|ay#awxYwwN)_use_lazy_graph_module_flagr)rrs r_use_lazy_graph_moduler&s2,+  AAA $ &+#e#s## #c&trtStSr)r_LazyGraphModulerr_get_graph_module_clsr4s: K KrN)graph_module_clsc*| t}||i|Sr)r)rargskwargss r_make_graph_moduler 9s!02 T ,V ,,rceZdZdZedefdZedZdZ edZ dZ e Z de fd Zd Zfd Zed Zed effd Zd effd ZxZS)ra! The main difference between _LazyGraphModule and GraphModule is how recompile happens. GraphModule will do a 'recompile' call to generate python code and the forward method when it's constructed. Later on if the graph get updated, recompile method can be called again to refresh the saved python code and forward method. However in some cases especially in inductor, the recompilation can be a waste since we never check the python code for the graph module or call its forward method. A few more concreate examples regarding pattern matching fx passes in inductor: 1. some passes will update the graph to be compiled and then call recompile on the GraphModule. 2. some passes will trace small pattern function to search it in the graph being compiled and replace the match with the traced graph of a replacement function. The pattern graph and replacement graph are quite small but there are large amount of them. Doing GraphModule.recompile for them in GraphModule.__init__ is also a waste of time. However simply skip calling GraphModule.recompile in these scenarios is also dangeruous. People may want to check the python code or call the GraphModule's forward method for debugging purposes. The way _LazyGraphModule solves it is, we override the recompile method to just mark the need for recompilation but does not do the actual recompilation. Later on if people really access the compiled python code or call the GraphModule's forward method, we do the real recompilation. gmcRt|tr|St||jSr) isinstancergraph)clsr"s rfrom_graphmodulez!_LazyGraphModule.from_graphmoduleZs# b* +I#B1 1rcFt|tr|jyy)z Sometimes we need force a recompile as a workaround - we want to do the real recompilation before symbolic_trace to avoid error: https://gist.github.com/shunting314/75549c2e82ae07ac1139c94a3583d259 N)r$rreal_recompile)r"s rforce_recompilez _LazyGraphModule.force_recompileas  b* +     ,rcF|jr|jyyr)_needs_recompile_real_recompile)selfs rr)z_LazyGraphModule.real_recompileks  "  " #rc2|j|juSr)forward _lazy_forwardr&s rr,z!_LazyGraphModule._needs_recompileos{{c////rcV|j|jrJ||i|Sr)r)r,)r.rrs rr1z_LazyGraphModule._lazy_forwardss4 ((*** T$V$$rexportercJ|j}|jj}|jj|d<|d=d|j }t |j|j}||jz}|j||t||ffS) Follow GraphModule.__reduce__ but call 'self._real_recompile' rather than 'self.recompile' since for a _LazyGraphModule, self.recompile just mark the need of recompilation and does not return the PythonCode object. _graphmodule_cls_name_graphzfx-generated._) r-__dict__copy __class____name__ get_unique_idrglobalsimportercodesave_source_stringr)r.r4 python_codedict_without_graphgenerated_module_name import_block module_codes r__reduce_package__z#_LazyGraphModule.__reduce_package__s **, !]]//16:nn6M6M23 x ("01G1G1I0J K+K,?,?ARARS "TYY. ##$9;G ' !6 7  rc|j}|jj}t|jt }|d=t ||ffS)r6r8)r-r9r:rr>r r)r.rBrCrEs r __reduce__z_LazyGraphModule.__reduce__sP **, !]]//1+K,?,?N x (#&8,%GHHrc t|Sr)super recompiler.r;s rr-z _LazyGraphModule._real_recompilesw ""rc&|j|_yr)r1r0r2s rrLz_LazyGraphModule.recompiles'' rreturnc8|jt|Sr)r)rKr@rMs rr@z_LazyGraphModule.codes w|rc@|jt| S)z str(GraphModule) will access the _code attribute. Make sure recompile happens so _code attribute is available. )r)rK__str__rMs rrRz_LazyGraphModule.__str__s w  r)r< __module__ __qualname____doc__ classmethodrr' staticmethodr*r)r,r1r0rrGrIr-rLpropertystrr@rR __classcell__)r;s@rrr@s02+22   #00 %G ? ( I#((c!!!rr) contextlibrtorch.fx.graph_modulerrrr torch.packagerr _compatibilityr rrrboolrrr rrrrr`s% 8)$%*"e,3-3"e, ,t ,- ,e,L-L04-e,x!{x!-x!r