o úÇ h«ã@sjddlZddlZejdd„ƒZejdd„ƒZejjZdd„Zdd „Z d d „Z d e e e effd d„ZdS)éNc cs@tj ¡}tj |¡z dVWtj |¡dStj |¡w)zlContext manager that controls whether the JIT's executor will run optimizations before executing a function.N)ÚtorchÚ_CÚ_get_graph_executor_optimizeÚ_set_graph_executor_optimize)Úshould_optimizeÚ stored_flag©rúd/var/www/html/construction_image-detection-poc/venv/lib/python3.10/site-packages/torch/jit/_fuser.pyÚoptimized_executions €  r c csœtj ¡}tj ¡}tj ¡}tj ¡}tj ¡}|dkr=tj d¡tj d¡tj  d¡tj  d¡tj  d¡n¬|dkrltj  d¡}tj  d¡}tj d¡tj d¡tj  d¡tj  d¡tj  d¡n}|dkrtj d¡tj d¡tj  d¡tj  d¡tj  d¡nZ|dkr¾tj  d¡}tj  d¡}tj d¡tj d¡tj  d¡tj  d¡tj  d¡n+|dkrátj d¡tj d¡tj  d¡tj  d¡tj  d¡ntd|›d ƒ‚z4d VW|d vrþtj  |¡tj  |¡tj |¡tj |¡tj  |¡tj  |¡tj  |¡d S|d vr/tj  |¡tj  |¡tj |¡tj |¡tj  |¡tj  |¡tj  |¡w) zúContext manager that facilitates switching between backend fusers. Valid names: * ``fuser0`` - enables only legacy fuser * ``fuser1`` - enables only NNC * ``fuser2`` - enables only nvFuser * ``fuser3`` - enables oneDNN Graph Úfuser0TFÚfuser1Úfuser2Úfuser3Únonez!unrecognized fuser option (name: ú)N)r r)rrÚ_jit_can_fuse_on_cpuÚ_jit_can_fuse_on_gpuÚ_jit_texpr_fuser_enabledÚ_jit_nvfuser_enabledÚ_jit_llga_enabledÚ_jit_override_can_fuse_on_cpuÚ_jit_override_can_fuse_on_gpuÚ_jit_set_texpr_fuser_enabledÚ_jit_set_nvfuser_enabledÚ_jit_set_llga_enabledÚ_jit_set_profiling_executorrÚ Exception)ÚnameÚ old_cpu_fuseÚ old_gpu_fuseÚold_texpr_fuser_stateÚold_nvfuser_stateÚold_llga_stateÚold_profiling_executorÚold_profiling_moderrr Úfusersv€                                   ø      r%cCsD| ¡dkr | |¡dS| ¡D]}| ¡D]}t||ƒqqdS)Nzprim::DifferentiableGraph)ÚkindÚappendÚblocksÚnodesÚ_get_differentiable_graph_node)ÚnodeÚ diff_nodeÚblockÚnrrr r*Vs    ÿÿr*cOst||g|¢Ri|¤ŽS)N)Ú_script_method_graph_for)ÚselfÚargsÚkwargsrrr Ú _graph_for_sr3c Osàz\| ¡}t|j ¡ƒ}t|ƒdksJ‚|dj ¡}|dj ¡}g}|  ¡D]} t | |ƒq(t|ƒt|ƒks:J‚t ||ƒD]\} } t| j ¡ƒ} t| ƒdkrY|   d| dj¡q?|WSt yo||i|¤ŽtƒYSw)NérÚSubgraph)Úget_debug_stateÚlistÚexecution_plansÚvaluesÚlenÚgraphÚcopyÚcodeÚ!differentiable_op_executor_statesr)r*ÚzipÚg_rÚlast_executed_optimized_graph) r0Úparentr1r2ÚdbsÚepsr;Ú fw_statesÚ diff_nodesr.ÚstateÚfw_execution_plansrrr r/cs(   €  ür/ÚstrategycCs tj |¡S)a[Set the type and number of specializations that can occur during fusion. Usage: provide a list of pairs (type, depth) where type is one of "STATIC" or "DYNAMIC" and depth is an integer. Behavior - static vs dynamic: In STATIC fusion, fused ops are compiled to have fixed input shapes. The shape is determined based on some initial profiling runs. In DYNAMIC fusion, fused ops are compiled to have variable input shapes, so that multiple shapes are possible. In both cases, we also recompile on new striding behavior, device, or dtype. Behavior - fallback functions & depth: When an input doesn't match the format required by the specialized compiled op, it will run a fallback function. Fallback functions are recursively be compiled and specialized based on the observed tensor shapes. Since compilation can be slow, the "depth" parameter is provided to limit the number of specializations that can be compiled, before giving up on recompiling and falling back to a completely un-fused, un-specialized implementation. The list of (type, depth) pairs controls the type of specializations and the number of specializations. For example: [("STATIC", 2), ("DYNAMIC", 2)] indicates that the first two specializations will use static fusions, the following two specializations will use dynamic fusion, and any inputs that satisfy none of the 4 options will run an unfused implementation. NB: in the future, if more as more fusion backends are added there may be more granular apis for specific fusers. )rrÚ_jit_set_fusion_strategy)rIrrr Úset_fusion_strategy‚s rK)Ú contextlibrÚcontextmanagerr r%rÚ_last_executed_optimized_graphrAr*r3r/r7ÚtupleÚstrÚintrKrrrr Ús  @