You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2019/12/04 01:04:22 UTC

[GitHub] [incubator-tvm] JennyChou5 commented on issue #4446: [RFC] Fixed-point type implementation proposal

JennyChou5 commented on issue #4446: [RFC] Fixed-point type implementation proposal
URL: https://github.com/apache/incubator-tvm/issues/4446#issuecomment-561427751
 
 
   agree with tqchen. The difference between fixed point and integer is that fixed point has fractional part while integer does not. By adding "point position (pp)" and adding dtype to quantization pass, we could reuse most of quantization API for the same matter. Of course, the TVM compute needs to be modified based on the value of the position. For example, aligning the pp before doing add operation; updating the pp after multiplication. In addition, I think it might not be good to have "func, params = relay.frontend.from_mxnet(block, shape_dict, "fxp16_13")" which means all models flows with same pp. Are you considering different pp in each layer since the precision loss and overflow may have impact on accuracy. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services