[BUG][Inductor-EVT] EVT python tracer: No LCA found when it appears that there is an LCA

Open
#2,309 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the linked reproduction script and the fn epilogue, then run it against the EVT Python tracer. Inspect how the tracer determines the LCA for E, F, tmp_2, and D. Done means this epilogue traces successfully instead of reporting that no LCA was found.

Written by the indexing model from the issue text.

Description

? - Needs Triage bug inactive-90d

Describe the bug
It looks like with the following epilogue code the tracer cannot find an LCA:

def fn(accum, bias):
    E = relu(accum)
    F = E + bias
    tmp_2 = E + 2
    D = tmp_2 + E
    return D

Although at first glance it looks like the LCA should be E? Unless I am misunderstanding something.

Steps/Code to reproduce bug
script

Expected behavior
I think this code should be traceable.

Environment details (please complete the following information):
meta devgpu, H100, CUTLASS commit: ad7b2f5e

cc @eellison, @thakkarV, @henrylhtsang, @mnicely

Dominant language
C++
Stars
10.5k
Forks
2.1k
Avg merge
3d 11h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/cutlass

All issues in NVIDIA/cutlass

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.