-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compile tch-rs against torch 2.1.0.dev #795
Comments
We only support using 2.0.0 at this stage (though 2.0.1 is likely to work), I plan on getting support for 2.1.0 once it has been a bit more crafted out so in a week or two (we're at RC2 so far I think). |
many thanks |
Hi, any updates on when we plan to support 2.1? (2.0.1 does work btw, I have tried) |
Still waiting on the actual release, my understanding was that it's scheduled for the 2023/10/04 so pretty soon but I haven't checked lately, I might start with the latest RC before that. |
I've started putting together #803 which should add support for v2.1.0 - the tests pass fine. I will wait for the official download links to be available before merging this version (this is scheduled for later this week afaik). |
Just merged #803 so now tch-rs is based on the just released PyTorch v2.1.0! |
Closing as hopefully all good now, the new crate is on crates.io. |
btw just curious, would the updated tch-rs be compatible with system that run on pytorch2.0? |
Nope, versions of tch-rs match exactly one version of pytorch/libtorch so you would have to downgrade the crate to support pytorch2.0 instead of 2.1. |
Whenever I call forward() repetitively to do inference, libtorch will crash within 10 cycles if libtorch version less than 2.0.1 or older is used. I accidentally find that this problem will not happen if I upgrade libtorch to 2.1.0.dev.
Because of this reason, I need to compile tch-rs with libtorch 2.1.0.dev. Before I do the compilation, I have done the followings:
I was then stuck at the following errors . Any pointers that help?
The text was updated successfully, but these errors were encountered: