-
Notifications
You must be signed in to change notification settings - Fork 868
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
API/ABI Compatibility #218
Comments
As for other libraries, breaking changes occur only when the major number changes. The NCCL API only changed between NCCL 1.x and NCCL 2.0. Note this is a general rule : the compiler will link applications against the major version of the library (i.e. Features can be added on any version, although main features would generally increase the minor number. Patches and small features (e.g. a new environment variable to control a setting) would usually only increase the patch number. Changes are noted in the git commit message, but you can also find release notes for the binaries provided on the developer zone : Let me know if that answers your question. |
Yep, this is exactly what I was looking for. Thanks for your detailed response, Sylvain. 🙂 |
Am curious what the intended API/ABI compatibility of NCCL is. When do breaking changes occur? When do new features get added? Is there backwards and/or forwards compatibility? How are these (and other) changes noted in the version?
The text was updated successfully, but these errors were encountered: