pytorch
Add support for int64_t indices and offsets in TBE inference [7B/N]
Summary: - Fix index_remapping in pruned_array_lookup to be int64_t always, since it is set up before we are provided indices and offsets
Differential Revision: D63567553
Deploy Preview for pytorch-fbgemm-docs ready!
| Name | Link |
|---|---|
| Latest commit | 5984c264c8c33df2c96d785b6727f6f59a8d3a2e |
| Latest deploy log | https://app.netlify.com/sites/pytorch-fbgemm-docs/deploys/66fb40c3e9c75d0008b4a585 |
| Deploy Preview | https://deploy-preview-3189--pytorch-fbgemm-docs.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @q10!
Thank you for your pull request.
We require contributors to sign our Contributor License Agreement, and yours needs attention.
You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.
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!