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
Hi, all.
Since it is an inquiry rather than an issue, I will not write a template.
Looking at the kernel side code of tflite, I saw that int4 for filter is supported in several op kernels; conv2d, depthwise-conv2d, fully-connected.
Could you tell me if there are plans to support int4 quantization in the tflite converter or support int4 for each op's input as well as filter, and if so, what milestones do you have?
Thank you :)
The text was updated successfully, but these errors were encountered:
This issue originally reported by @0-chan-kor has been moved to this dedicated repository for LiteRT to enhance issue tracking and prioritization. To ensure continuity, we have created this new issue on your behalf.
We appreciate your understanding and look forward to your continued involvement.
Hi, all.
Since it is an inquiry rather than an issue, I will not write a template.
Looking at the kernel side code of tflite, I saw that int4 for filter is supported in several op kernels; conv2d, depthwise-conv2d, fully-connected.
Could you tell me if there are plans to support int4 quantization in the tflite converter or support int4 for each op's input as well as filter, and if so, what milestones do you have?
Thank you :)
The text was updated successfully, but these errors were encountered: