o "i@s8ddlmZmZgdZgdZeddgeedddged d ed d d geddedeeddedeedddgedddgeddgeddgeddeddd geed!d"d#d$ed%d&d#d'ed(d)d#d'ed*d+ed,d-ed.d/ed0d1ed2d3ed4d5ed6d7d#d$ed8d9ed:d;edd?d#d'ed@dAedBdCd#d$edDdEd#d#dFedGdHd#d$edIdJedKdLd#d#dMedNdOd#d#dMedPdQd#d'edRd&d#d'edSd&d#d'edTdUd#d'edVdWd#d'edXdYd#d'edZd[d&d\d]S)^)register_artifact register_log)z%torch.fx.experimental.symbolic_shapesztorch.fx.experimental.sym_nodeztorch.fx.experimental.recording)ztorch.distributed"torch._dynamo.backends.distributedtorch.nn.parallel.distributeddynamoz torch._dynamoaotztorch._functorch.aot_autogradztorch._functorch._aot_autogradautogradztorch.autogradinductorztorch._inductorztorch._inductor.cudagraph_trees cudagraphszGLogs information from wrapping inductor generated code with cudagraphs.dynamictorch distributedc10dz"torch.distributed.distributed_c10dztorch.distributed.rendezvousddprrppztorch.distributed.pipeliningfsdpztorch.distributed.fsdponnxz torch.onnxexportz torch.exportguardszhThis prints the guards for every compiled Dynamo frame. It does not tell you where the guards come from.T)visibleverbose_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. graph_codez4Like `graph`, but gives you the Python code instead. graph_sizesz5Prints the sizes of all FX nodes in the dynamo graph. trace_sourcezAs we execute bytecode, prints the file name / line number we are processing and the actual source code. Useful with `bytecode` trace_callzhLike trace_source, but it will give you the per-expression blow-by-blow if your Python is recent enough.trace_bytecodezCAs we trace bytecode, prints the instruction and the current stack. aot_graphszPrints the FX forward and backward graph generated by AOTDispatch, after partitioning. Useful to understand what's being given to Inductoraot_joint_graphz_Print FX joint graph from AOTAutograd, prior to partitioning. Useful for debugging partitioningpost_grad_graphsz}Prints the FX graph generated by post grad passes. Useful to understand what's being given to Inductor after post grad passescompiled_autogradzzPrints various logs in compiled_autograd, including but not limited to the graphs. Useful for debugging compiled_autograd.compiled_autograd_verbosezjWill affect performance. Prints compiled_autograd logs with C++ info e.g. autograd node -> fx node mapping ddp_graphszOnly relevant for compiling DDP. DDP splits into multiple graphs to trigger comms early. This will print each individual graph here. recompilesz?Prints the reason why we recompiled a graph. Very, very useful.recompiles_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 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 to output_codez>Prints the code that Inductor generates (either Triton or C++))rr kernel_codez?Prints the code that Inductor generates (on a per-kernel basis)schedulezIInductor scheduler information. Useful if working on Inductor fusion algo perf_hintsonnx_diagnosticsfusionzADetailed Inductor fusion decisions. More detailed than 'schedule'overlapz0Detailed Inductor compute/comm overlap decisionssym_nodez.Logs extra info for various SymNode operationscustom_format_test_artifactz Testing only) log_formatN) _internalrrDYNAMIC DISTRIBUTEDr7r7[/home/ubuntu/SoloSpeech/.venv/lib/python3.10/site-packages/torch/_logging/_registrations.pys