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 2022/09/29 01:33:31 UTC

[GitHub] [tvm] t-vi commented on pull request #7401: RFC: initial stab at TorchScript fallback

t-vi commented on PR #7401:
URL: https://github.com/apache/tvm/pull/7401#issuecomment-1261635641

   The fundamental problem is that (pre-compiled) PyTorch python modules use the pre C++-11 string ABI to better blend into the Python ecosystem or so. TVM does not, so it needs to link to LibTorch with the "new" C++ string ABI.
   But these two versions clash.
   
   One option is to use self-compiled PyTorch (which is what I do and so got us into this mess...).
   
   I've been trying on and off to look into linking LibTorch such that all symbols are hidden (and you can load PyTorch with whatever C++ ABI later), but I have not managed yet.


-- 
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-unsubscribe@tvm.apache.org

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