You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we debug Fusions generated by the framework, we don't know why a set of instructions exist together in the fusion group and then those instructions get segmented into multiple kernels and we are left needing to figure out why we are segmenting the fusion into multiple kernels from the top down. It would be nice if the segment information was captured in the Fusion IR dump instead of requiring a separate set of information to determine what is being grouped.
Scheduled Fusion IR (the math only without the transforms of the tensors): It looks like the printing of the segments is not cleanly separated in stdout.
Command:
Segmentation Fusion IR Debug: It is not clear where the groups are coming from original pre-scheduled Fusion IR. Since this case only has 2 operations, it is easy to infer. It would be nice if segmentation information was naturally just printed with the Fusion IR instead of requiring a separate debug output. As we take in larger fusion groups, it is going to be more likely that we will segment operations.
When we debug Fusions generated by the framework, we don't know why a set of instructions exist together in the fusion group and then those instructions get segmented into multiple kernels and we are left needing to figure out why we are segmenting the fusion into multiple kernels from the top down. It would be nice if the segment information was captured in the Fusion IR dump instead of requiring a separate set of information to determine what is being grouped.
Here is a simplified example:
Python Definition:
Pre-scheduled Fusion IR:
Command:
Scheduled Fusion IR (the math only without the transforms of the tensors):
It looks like the printing of the segments is not cleanly separated in stdout.
Command:
Segmentation Fusion IR Debug:
It is not clear where the groups are coming from original pre-scheduled Fusion IR. Since this case only has 2 operations, it is easy to infer. It would be nice if segmentation information was naturally just printed with the Fusion IR instead of requiring a separate debug output. As we take in larger fusion groups, it is going to be more likely that we will segment operations.
Command:
The real example of the fusion definition from the backward implementation of Gelu + a Bias Gradient.
The text was updated successfully, but these errors were encountered: