VhB8dZddlmZddlZddlZddlmZddlZddlm Z ddl m Z m Z ddl mZddlmZerdd lmZddd ZGd d e j*ZGd dZeZej2aej6ddZ d ddZddZy)zRDiagnostic components for TorchScript based ONNX export, i.e. `torch.onnx.export`.) annotationsN) TYPE_CHECKING)infra) formattersarif)version) cpp_backtrace) Generatorc tj||jd}g}|D]V}|jdd}t|dk(r#|j |dj F|j dXt j|Dcgc],}t jt j|.c}Scc}w) avReturns the current C++ call stack. This function utilizes `torch.utils.cpp_backtrace` to get the current C++ call stack. The returned C++ call stack is a concatenated string of the C++ call stack frames. Each frame is separated by a newline character, in the same format of r"frame #[0-9]+: (?P.*)". More info at `c10/util/Backtrace.cpp`.  :z)message)location)frames) r get_cpp_backtracesplitlenappendstriprStack StackFrameLocation)frames_to_skip frames_to_logrframe_messagesframesegmentsrs \/home/dcms/DCMS/lib/python3.12/site-packages/torch/onnx/_internal/diagnostics/_diagnostic.py_cpp_call_stackr!s , ,^] K Q QRV WFN5;;sA& x=A   ! !(1+"3"3"5 6  ! !"3 4 5 ;;*    ennW&E F   s1Cc\eZdZUdZdZded<dZded<ddd d fd Zd d ZxZ S) TorchScriptOnnxExportDiagnosticzBase class for all export diagnostics. This class is used to represent all export diagnostics. It is a subclass of infra.Diagnostic, and adds additional methods to add more information to the diagnostic. Nzinfra.Stack | Nonepython_call_stackcpp_call_stackrF)r cpp_stackct||i||j||_|r|j ||_yy)Nr)super__init__record_python_call_stackr$record_cpp_call_stackr%)selfrr&argskwargs __class__s r r*z(TorchScriptOnnxExportDiagnostic.__init__9sW $)&)!%!>!>)"?"  "&"<"<-#=#D  cNt|}d|_|j||S)z5Records the current C++ call stack in the diagnostic.r(zC++ call stack)r!r with_stack)r-rstacks r r,z5TorchScriptOnnxExportDiagnostic.record_cpp_call_stackIs$~>(   r1)rintr&boolreturnNone)rr5r7 infra.Stack) __name__ __module__ __qualname____doc__r$__annotations__r%r*r, __classcell__)r0s@r r#r#.sQ-1)0)-N&-       r1r#cxeZdZUdZded<ded<ddZeddZ d dd Zd Z dd Z ddd Z d Z y)ExportDiagnosticEngineaFPyTorch ONNX Export diagnostic engine. The only purpose of creating this class instead of using `DiagnosticContext` directly is to provide a background context for `diagnose` calls inside exporter. By design, one `torch.onnx.export` call should initialize one diagnostic context. All `diagnose` calls inside exporter should be made in the context of that export. However, since diagnostic context is currently being accessed via a global variable, there is no guarantee that the context is properly initialized. Therefore, we need to provide a default background context to fallback to, otherwise any invocation of exporter internals, e.g. unit tests, will fail due to missing diagnostic context. This can be removed once the pipeline for context to flow through the exporter is established. zlist[infra.DiagnosticContext]contextsinfra.DiagnosticContext_background_contextcfg|_tjdtj|_y)Nz torch.onnx)namer)rBrDiagnosticContexttorch __version__rDr-s r r*zExportDiagnosticEngine.__init__ds( #(#:#:%%$  r1c|jSN)rDrJs r background_contextz)ExportDiagnosticEngine.background_contextks'''r1Nc|tj}tj|||}|jj ||S)a2Creates a new diagnostic context. Args: name: The subject name for the diagnostic context. version: The subject version for the diagnostic context. options: The options for the diagnostic context. Returns: A new diagnostic context. )rDiagnosticOptionsrGrBr)r-rFroptionscontexts r create_diagnostic_contextz0ExportDiagnosticEngine.create_diagnostic_contextosG ?--/G=B=T=T '7>  W%r1c|jj|jjjy)zClears all diagnostic contexts.N)rBclearrD diagnosticsrJs r rTzExportDiagnosticEngine.clears*    ,,224r1cHtj|jSrL)r sarif_to_json sarif_logrJs r to_jsonzExportDiagnosticEngine.to_jsons&&t~~'788r1c|r?tj|d5}|j|jdddyt|d5}|j|jdddy#1swYyxYw#1swYyxYw)zDumps the SARIF log to a file.wtNw)gzipopenwriterY)r- file_pathcompressfs r dumpzExportDiagnosticEngine.dumps{ 9d+ (q ' ( (i% ( ' ( ( ( ( ( (s A7 B7BB c *tjtjtj|j Dcgc]}|jc}}|j j|jj|Scc}w)N)r schema_uriruns) rSarifLog sarif_version SARIF_VERSIONSARIF_SCHEMA_LINKrBrfrrD)r-rQlogs r rXz ExportDiagnosticEngine.sarif_logsfnn!//$6615?g'--/?  006689 @sB )r7r8r7rCrL)rFstrrrmrPzinfra.DiagnosticOptions | Noner7rC)r7rm)F)r`rmrar6r7r8) r:r;r<r=r>r*propertyrMrRrTrYrcrXr1r rArAQsr ,+00 ((37 0  ! 05 9(r1rAc#Kttjk(sJdtjdtj a ttjay#tjawxYww)zCreate a diagnostic context for export. This is a workaround for code robustness since diagnostic context is accessed by export internals via global variable. See `ExportDiagnosticEngine` for more details. z>Export context is already set. Nested export is not supported.ztorch.onnx.exportN)_contextenginerMrRrHrIror1r create_export_diagnostic_contextrssd v00 0H 0// H-,,6,,sAA4AA4A11A4c Xt|||fd|i|}tj||S)zCreates a diagnostic and record it in the global diagnostic context. This is a wrapper around `context.log` that uses the global diagnostic context. r)r#export_contextrk)rulelevelrrr/ diagnostics r diagnoserys>1 eW-;?EJ$ r1ctSrL)rqror1r rurus Or1)r )rr5rr5r7r9)r7z.Generator[infra.DiagnosticContext, None, None])Nr) rvz infra.Rulerwz infra.Levelrz str | Nonerr5r7r#rl)r= __future__r contextlibr]typingrrH torch.onnx._internal.diagnosticsr&torch.onnx._internal.diagnostics.infrarr,torch.onnx._internal.diagnostics.infra.sarifrrh torch.utilsr collections.abcr r! Diagnosticr#rArrrMrqcontextmanagerrsryruror1r rsX" 2CQ%)2 e&6&6 FOOd !  $ $ --2     % &r1