[GitHub] [tvm] yongwww commented on issue #4102: [Relay] Support for Tensorflow 2.0

2022-01-12 Thread GitBox


yongwww commented on issue #4102:
URL: https://github.com/apache/tvm/issues/4102#issuecomment-1011238146


   > Hi! What is the status of Tensorflow2 support or schedule for it?
   > 
   > We use Tensorflow 2.x. Should TVM users still convert models back to 
TF1.12 or can we go with TF2 models? (At least 
https://tvm.apache.org/docs/dev/frontend/tensorflow.html still refers to 
TF1.12...)
   
   TensorFlow 2.x is supported in TVM, no need to convert models back to TF 
1.x. 


-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@tvm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [tvm] yongwww commented on issue #4102: [Relay] Support for Tensorflow 2.0

2021-03-09 Thread GitBox


yongwww commented on issue #4102:
URL: https://github.com/apache/tvm/issues/4102#issuecomment-794649484


   I agree with the main ideas you guys proposed above. @srkreddy1238 @wx3000 
Having a common .py for op mapping for both v1 and v2, exclusive ops go to 
individual parsers (v1, v2).



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:
us...@infra.apache.org




[GitHub] [tvm] yongwww commented on issue #4102: [Relay] Support for Tensorflow 2.0

2020-12-10 Thread GitBox


yongwww commented on issue #4102:
URL: https://github.com/apache/tvm/issues/4102#issuecomment-742463914


   @srkreddy1238 yeah, I agree that GraphDef protocol buffer definition just 
changed a little, creating a new parser will end up with some redundant work 
(copy from the existing parser). I tried to run the test cases in your shared 
branch, I found the existing parser works for most of the TF 2.x ops 
(previously I assume we have to modify most of the mapping in the parser). 
   
   I agree that we can just update the existing parser for TF2.x, and remove 
unnecessary part in the future once we stop supporting 1.x support. 
   
   Please rebase your work, it would be good to have it work on top of TF 
2.4(latest version is 2.4.0rc4). We can work on variable and tensorlist related 
ops at the same time. 



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:
us...@infra.apache.org




[GitHub] [tvm] yongwww commented on issue #4102: [Relay] Support for Tensorflow 2.0

2020-12-03 Thread GitBox


yongwww commented on issue #4102:
URL: https://github.com/apache/tvm/issues/4102#issuecomment-738507269


   We have looked into the models like image classification, object detection, 
segmentation, etc. Seems we need to enable the support for TensorList, 
control-flow, function, and some missing operations. We would like to work on 
this project from scratch.  As we discussed above, we might create a new tf 
frontend for tf2.x (and I believe the parser for tf1.x will be deprecated in 
the future as tf community stops the support for 1.x).
   
   Please comment here or ping me/us if anyone is interested in working with us 
on this. I synced with siva @srkreddy1238 in the past few weeks, we will keep 
him and the community updated if we work together on this.



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:
us...@infra.apache.org