🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/806

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 8b79caa with merge base f5703b0 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

Hi @Ali-Flt!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

thanks! Could you also add a test to https://github.com/pytorch/ao/blob/main/test/prototype/mx_formats/test_mx_linear.py ?

@vkuzo I tried different ways to trigger the use of aten.linear but couldn't

I'd definitely recommend a test that fails before this PR and passes after this PR. Would it work to wrap the code snippet you were using (which ended up calling into the linear override) into a test?

Just curious. Would it be better to implement F.linear() under __torch_function__() instead? Previously I also faced strange behavior on what aten ops will be dispatched by F.linear(), so implementing F.linear() directly would solve the problem.

Would it be better to implement F.linear() under torch_function() instead?

As of ~months ago, __torch_dispatch__ was better supported with torch.compile, at least for the things we needed for float8. I haven't checked if torch.compile + __torch_function__ coverage is better now, would be good to check.