tilelang-pass-workflow-analyzer

To analyze TileLang-Ascend Pass pipeline dependencies, prioritize reading reference documents like pass-dependency-graph.md to map Pass-to-Pass data flow such as buffer scope to CrossCorePipeline before checking source code.

Inserting a new pass in the TileLang-Ascend compiler workflow requires diagnosing phase dependencies to recommend exact Phase 1 or Phase 2 positions, such as placing memory optimization passes after AscendStorageRewrite and before AscendMemoryPlanning.

Cross-pass data flow for buffer_shapes and address_map in TileLang follows dependency sequences like CollectBufferShapes to AscendMemoryPlanning to AscendSyncInsert, ensuring cross-phase attributes are respected during pipeline execution.

The two-phase workflow in the TileLang-Ascend compiler organizes Pass execution order into distinct phases, allowing engineers to diagnose phase dependencies and safely plan new pass placement without breaking the pipeline.

Reading source code directly to understand TileLang pass placement is not recommended initially; you should prioritize reference documents like new-pass-placement-guide.md and only drill down into files like tilelang/engine/phase.py when concrete implementation details are needed.

Ignoring pass dependencies when modifying the TileLang pipeline breaks cross-phase attributes like buffer scope and size_map, which is why dependency-aware placement recommendations are necessary to maintain valid execution order.