o ÔÙ¾i¥ã@sVddlZddlmZddlmZddlmZmZmZm Z e  e ¡Z Gdd„deƒZ dS)éN)Úfx)ÚFixFunctionalizationPass)ÚCustomGraphPassÚ InductorPassÚSGLangInductorPassÚget_pass_contextc@sFeZdZdZdd„Zdejfdd„Zdd„Zd e fd d „Z d d „Z dS)ÚPostGradPassManagera$ The pass manager for post-grad passes. It handles configuration, adding custom passes, and running passes. It supports uuid for the Inductor code cache. That includes torch<2.6 support using pickling (in .inductor_pass.CustomGraphPass). The order of the post-grad post-passes is: 1. passes (constructor parameter) 2. default passes (NoopEliminationPass, FusionPass) 3. config["post_grad_custom_post_pass"] (if it exists) 4. fix_functionalization This way, all passes operate on a functionalized graph. cCs g|_dS©N)Úpasses©Úself©r úW/home/ubuntu/.local/lib/python3.10/site-packages/sglang/srt/compilation/pass_manager.pyÚ__init__!s zPostGradPassManager.__init__ÚgraphcCs4tƒj}|jD] }| |¡r||ƒq| |¡dSr )rÚ runtime_shaper Úis_applicable_for_shapeÚfix_functionalization)r rÚshapeÚpass_r r rÚ__call__$s   €zPostGradPassManager.__call__cCstƒ|_tƒ|_dSr )ÚdictÚ pass_configrrr r r rÚ configure-s zPostGradPassManager.configurercCst|tƒsJ‚|j |¡dSr )Ú isinstancerr Úappend)r rr r rÚadd3szPostGradPassManager.addcCsJd}|gdœ}|jD] }|d | ¡¡q |d |j ¡¡t |¡S)zí The PostGradPassManager is set as a custom pass in the Inductor and affects compilation caching. Its uuid depends on the UUIDs of all dependent passes and the pass config. See InductorPass for more info. Ú fshdakhsa)rr r )r rÚuuidrrÚ hash_dict)r Úpass_manager_uuidÚstaterr r rr7s    zPostGradPassManager.uuidN) Ú__name__Ú __module__Ú __qualname__Ú__doc__rrÚGraphrrrrrr r r rrs  r)ÚloggingÚtorchrÚ,sglang.srt.compilation.fix_functionalizationrÚ$sglang.srt.compilation.inductor_passrrrrÚ getLoggerr"Úloggerrr r r rÚs