U yh@s6ddlmZmZdddgZdddgZedd`eed d d ged dedddgeddedeeddedeedddgedddgeddgeddgedd ed!daeed#d$d%d&ed'd(d%d)ed*d+d%d)ed,d-ed.d/ed0d1ed2d3ed4d5ed6d7ed8d9d%d&ed:d;edd?d%d&ed@dAd%d)edBdCedDdEd%d&edFdGd%d%dHedIdJd%d&edKdLedMdNd%d%dOedPdQd%d%dOedRdSd%d)edTd(d%d)edUd(d%d)edVdWd%d)edXdYd%d)edZd[d%d)ed\d]d(d^d_S)b)register_artifact register_logz%torch.fx.experimental.symbolic_shapesztorch.fx.experimental.sym_nodeztorch.fx.experimental.recordingztorch.distributedz"torch._dynamo.backends.distributedztorch.nn.parallel.distributedZdynamo torch._dynamoZaotztorch._functorch.aot_autogradztorch._functorch._aot_autogradZautogradztorch.autogradZinductorztorch._inductorztorch._inductor.cudagraph_treesZ cudagraphszGLogs information from wrapping inductor generated code with cudagraphs.ZdynamicZtorch distributedZc10dz"torch.distributed.distributed_c10dztorch.distributed.rendezvousZddpppztorch.distributed.pipeliningZfsdpztorch.distributed.fsdpZonnxz torch.onnxZexport torch.exportZguardszhThis prints the guards for every compiled Dynamo frame. It does not tell you where the guards come from.T)visibleZverbose_guards)off_by_defaultbytecodez{Prints the original and modified bytecode from Dynamo. Mostly useful if you're debugging our bytecode generation in Dynamo.graphzvPrints the dynamo traced graph (prior to AOTDispatch) in a table. If you prefer python code use `graph_code` instead. Z graph_codez4Like `graph`, but gives you the Python code instead.Z graph_sizesz5Prints the sizes of all FX nodes in the dynamo graph.Z trace_sourcezAs we execute bytecode, prints the file name / line number we are processing and the actual source code. Useful with `bytecode`Z trace_callzhLike trace_source, but it will give you the per-expression blow-by-blow if your Python is recent enough.Ztrace_bytecodezCAs we trace bytecode, prints the instruction and the current stack.Z aot_graphszPrints the FX forward and backward graph generated by AOTDispatch, after partitioning. Useful to understand what's being given to InductorZaot_joint_graphz_Print FX joint graph from AOTAutograd, prior to partitioning. Useful for debugging partitioningZpost_grad_graphsz}Prints the FX graph generated by post grad passes. Useful to understand what's being given to Inductor after post grad passesZcompiled_autogradzzPrints various logs in compiled_autograd, including but not limited to the graphs. Useful for debugging compiled_autograd.Zcompiled_autograd_verbosezjWill affect performance. Prints compiled_autograd logs with C++ info e.g. autograd node -> fx node mappingZ ddp_graphszOnly relevant for compiling DDP. DDP splits into multiple graphs to trigger comms early. This will print each individual graph here.Z recompilesz?Prints the reason why we recompiled a graph. Very, very useful.Zrecompiles_verbosezPrints all guard checks that fail during a recompilation. At runtime, Dynamo will stop at the first failed check for each failing guard. So not all logged failing checks are actually ran by Dynamo.)rr Z graph_breakszPrints whenever Dynamo decides that it needs to graph break (i.e. create a new graph). Useful for debugging why torch.compile has poor performancenot_implementedzPrints log messages whenever we return NotImplemented in a multi-dispatch, letting you trace through each object we attempted to dispatch toZ output_codez>Prints the code that Inductor generates (either Triton or C++))r rZ kernel_codez?Prints the code that Inductor generates (on a per-kernel basis)ZschedulezIInductor scheduler information. Useful if working on Inductor fusion algoZ perf_hintsZonnx_diagnosticsZfusionzADetailed Inductor fusion decisions. More detailed than 'schedule'Zoverlapz0Detailed Inductor compute/comm overlap decisionsZsym_nodez.Logs extra info for various SymNode operationsZcustom_format_test_artifactz Testing only)Z log_formatN)r)rr) _internalrrZDYNAMICZ DISTRIBUTEDrrO/var/www/html/venv/lib/python3.8/site-packages/torch/_logging/_registrations.pys"