Improve reasoning for size oblivious equations involving max() #125914
Labels
high priority
module: dynamic shapes
oncall: pt2
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
馃悰 Describe the bug
Internal xref: https://fb.workplace.com/groups/6829516587176185/posts/7172183699576137/
This program fails to compile:
Actually, we should be able to make the inference here, because u0 and u1 are size-like in a size oblivious, so we assume they are >= 2, which means that the Max should evaporate, but we are unable to do this.
cc @gchanan @zou3519 @kadeng @msaroufim @bdhirsh @anijain2305 @chauhang @lezcano
Versions
main
The text was updated successfully, but these errors were encountered: